Re: Logical replication can lose an update after concurrent index invalidation - Mailing list pgsql-hackers

From vignesh C
Subject Re: Logical replication can lose an update after concurrent index invalidation
Date
Msg-id CALDaNm3m44D8O68iJoigYVLV0A5qmxBCbbABpd9bqDmkxVcwZA@mail.gmail.com
Whole thread
In response to Re: Logical replication can lose an update after concurrent index invalidation  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, 22 Sept 2026 at 15:33, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Sep 21, 2026 at 6:01 PM vignesh C <vignesh21@gmail.com> wrote:
> >
> > Here is an updated version including the back-branches version.
> > This version also addresses Hou-san's agreed 1st comment from [1].
> >
>
> We should include the test till the version where required Injection
> Point functionality is present.

Here is an updated version with the injection point and its test added
up to the PG17 version, where injection points were introduced.
I have also retained the DROP INDEX CONCURRENTLY test instead of the
REINDEX CONCURRENTLY test, as the former requires only one injection
point (apply-update-before-open-indices), whereas the latter requires
two injection points: reindex-relation-concurrently-before-swap and
apply-update-before-open-indices.

Regards,
Vignesh

Attachment

pgsql-hackers by date:

Previous
From: Jeevan Chalke
Date:
Subject: Re: Use-after-free of a shared Path in add_path()/add_partial_path()
Next
From: Antonin Houska
Date:
Subject: Re: REPACK enhancements