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

From Zhijie Hou (Fujitsu)
Subject RE: Conflict detection for update_deleted in logical replication
Date
Msg-id OS9PR01MB169139908EC924856F187825F940CA@OS9PR01MB16913.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Conflict detection for update_deleted in logical replication  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Monday, September 8, 2025 3:13 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> 
> On Fri, Sep 5, 2025 at 5:03 PM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
> wrote:
> >
> > Here are v2 patches which addressed above comments.
> >
> 
> I have pushed the first patch. I find that the test can't reliably fail without a fix.
> Can you please investigate it?

Thank you for catching this issue. I confirmed that the test may have tested
VACCUM before slot.xmin was advanced. Therefore, to improve the test, I modified
test to wait for the publisher's request message appearing twice, as after the
fix, the apply worker should keep waiting for publisher status until the
prepared txn is committed.

Also, to reduce test time, I moved the test into the existing 035 test.

Here is the updated test.

Best Regards,
Hou zj

Attachment

pgsql-hackers by date:

Previous
From: David Geier
Date:
Subject: Re: Use merge-based matching for MCVs in eqjoinsel
Next
From: Vivek Gadge
Date:
Subject: Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6