Horton

Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL

Peter Smith <smithpb2250@gmail.com>

View thread View on postgr.es
From: Peter Smith <smithpb2250@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Önder Kalacı <onderkalaci@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-27T01:06:25Z
Lists: 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

Commits

  1. Allow the use of a hash index on the subscriber during replication.

  2. Allow the use of indexes other than PK and REPLICA IDENTITY on the subscriber.