Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
От | Amit Kapila |
---|---|
Тема | Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL |
Дата | |
Msg-id | CAA4eK1LAv=o4MHFLWp_x6AfLXbtCa704N2teAVQc7C4GQoftAg@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>) |
Ответы |
RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
|
Список | 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.
В списке pgsql-hackers по дате отправления: