Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@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-07-08T05:36:49Z
Lists: pgsql-hackers
On Fri, Jul 7, 2023 at 1:31 PM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Thank you for your analysis! > > > > Yes, I agree, it is (and was before my patch as well) un-documented limitation of REPLICA IDENTITY FULL. > And, as far as I can see, my patch actually didn't have any impact on the limitation. The unsupported > cases are still unsupported, but now the same error is thrown in a slightly different place. > I think that is a minor limitation, but maybe should be listed [1]? > > +1. > > Yes, your modification did not touch the restriction. It has existed before the > commit. I (or my colleague) will post the patch to add the description, maybe > after [1] is committed. > I don't think there is any dependency between the two. So, feel free to post the patch separately. -- With Regards, Amit Kapila.
Commits
-
Allow the use of a hash index on the subscriber during replication.
- edca3424342d 17.0 landed
-
Allow the use of indexes other than PK and REPLICA IDENTITY on the subscriber.
- 89e46da5e511 16.0 cited