Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Date
Msg-id CAA4eK1JjUKbLZzfSX2p73kfOjSBJzSmV+kYxcCo_Ke5P=fKEYg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
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.

--
With Regards,
Amit Kapila.

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: "current directory" in a server error message
Next
From: Julien Rouhaud
Date:
Subject: Re: pg_dump versus hash partitioning