Re: Proposal: Conflict log history table for Logical Replication - Mailing list pgsql-hackers

From Zhijie Hou
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAFvd2n92EXzt7VNRGxQCMkK1t2+6RA9SwQ5j9DHMwJcWCNoK1Q@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Proposal: Conflict log history table for Logical Replication
List pgsql-hackers
Hi,

On Sun, Oct 4, 2026 at 5:01 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
>
> And without fix shared as a v77-0003 [1], this would error out with
> below error[2], I have explained the reason [1].  I have added a
> testcase in 035_conflicts.pl file in v79-0003 patch for this issue.

Thanks for updating the patches.

I've started reviewing the 0001 patch and would like to suggest some refactoring
to simplify the code in ReportApplyConflict(). The idea is to move the fallback
logic into get_conflictlog_dest_and_table() so the caller's code looks cleaner.

And I think we could build the errdetail for both the table and
logfile cases and call ereport() only once, to reduce the duplicated code.

Please check the attached follow-up patches (on top of 0001), I hope it makes
the code better.(1 file changed, 33 insertions(+), 58 deletions(-))

Best Regards,
Zhijie Hou

Attachment

pgsql-hackers by date:

Previous
From: solai v
Date:
Subject: Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)
Next
From: Masahiko Sawada
Date:
Subject: Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers