| From: | Mike L <giantmetfan(at)comcast(dot)net> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: logical replication issue |
| Date: | 2025-04-17 15:52:02 |
| Message-ID: | D8690293-22E3-4656-8C54-78433EC4A996@comcast.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks Tom. These tables with this issue are related to Arcgis. I cannot modify existing tables by adding primary keys if it doesn't already have one.
Will have to exclude these tables from replication it appears.
On April 17, 2025 11:05:25 AM EDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Mike L <giantmetfan(at)comcast(dot)net> writes:
>> Should logical replication fail due to a column of type 'xml' in a table
>> in a publication?
>
>Well, as you note, there's no equality operator for type xml.
>
>Looking at the replication code, it looks like you might be able
>to dodge the error if the replicated-to table has a primary key
>(which'd necessarily not involve the xml column). Without a PK,
>it will do full-row equality checks to determine tuple matches,
>and that's where it falls down trying to compare the xml column.
>
> regards, tom lane
>
>
Mike L
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kellyn Pot'Vin-Gorman | 2025-04-17 20:28:37 | Re: Replication lag |
| Previous Message | Tom Lane | 2025-04-17 15:05:25 | Re: logical replication issue |