Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
От | Amit Kapila |
---|---|
Тема | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |
Дата | |
Msg-id | CAA4eK1LmdYY1M-hwYzx08Y164Gi-Jrgs5ts0GmEmcfTu1G7Rtg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Thu, Mar 16, 2023 at 2:15 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Wed, Mar 15, 2023 at 9:12 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Tue, Mar 14, 2023 at 3:18 PM Önder Kalacı <onderkalaci@gmail.com> wrote: > > >> > > > > Pushed this patch but forgot to add a new testfile. Will do that soon. > > > > The main patch is committed now. I think the pending item in this > thread is to conclude whether we need a storage or subscription to > disable/enable this feature. Both Andres and Onder don't seem to be in > favor but I am of opinion that it could be helpful in scenarios where > the index scan (due to duplicates or dead tuples) is slower. However, > if we don't have a consensus on the same, we can anyway add it later. > If there are no more votes in favor of adding such an option, we can > probably close the CF entry. > I have closed this CF entry for now. However, if there is any interest in pursuing the storage or subscription option for this feature, we can still discuss it. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: