Re: Conflict detection for update_deleted in logical replication - Mailing list pgsql-hackers

From Michail Nikolaev
Subject Re: Conflict detection for update_deleted in logical replication
Date
Msg-id CANtu0ohzMB38tcf2=q1HVCdz+eEpBBauHhMoATz_=YFEjDd7FQ@mail.gmail.com
Whole thread Raw
In response to Re: Conflict detection for update_deleted in logical replication  (Nisha Moond <nisha.moond412@gmail.com>)
Responses RE: Conflict detection for update_deleted in logical replication
List pgsql-hackers
Hello, Hayato!

> Thanks for updating the patch! While reviewing yours, I found a corner case that
> a recently deleted tuple cannot be detected when index scan is chosen.
> This can happen when indices are re-built during the replication.
> Unfortunately, I don't have any solutions for it.

I just randomly saw your message, so, I could be wrong and out of the context - so, sorry in advance.

But as far as I know, to solve this problem, we need to wait for slot.xmin during the [0] (WaitForOlderSnapshots) while creating index concurrently.


Best regards,
Mikhail.

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: type cache cleanup improvements
Next
From: Amit Kapila
Date:
Subject: Re: Pgoutput not capturing the generated columns