Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL - Mailing list pgsql-hackers

From Peter Smith
Subject Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
Date
Msg-id CAHut+Ps8+w=sMFN3DdogREyeZO4ouJfwMSJoJtgNTkLdU9HATQ@mail.gmail.com
Whole thread Raw
In response to RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
On Mon, Jun 26, 2023 at 11:44 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
...
> BTW, I have doubt that the restriction is not related with your commit.
> In other words, if the table has attributes which the datatype is not for operator
> class of Btree, we could not use REPLICA IDENTITY FULL. IIUC it is not documented.
> Please see attched script to reproduce that. The final DELETE statement cannot be
> replicated at the subscriber on my env.
>

Missing attachment?

------
Kind Regards,
Peter Smith.
Fujitsu Australia



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL