Conflict detection for multiple_unique_conflicts in logical replication

Hi Hackers, (CCing people involved in related discussions) I am starting this thread to propose a new conflict detection type "multiple_unique_conflicts" that identifies when an incoming row during logical replication violates more than one UNIQUE constraint. If multiple constraints (such as the p

Re: ReplicationSlotRelease() crashes when the instance is in the single user mode

On Thu, Feb 20, 2025 at 4:26 PM Zhijie Hou (Fujitsu) wrote: > > On Thursday, February 20, 2025 10:23 AM Hayato Kuroda (Fujitsu) > wrote: > > > > Dear Michael, > > > > > I did not check how these call behave individually, just a few > > > comments while putting my eyes on the patch. > > > > > > +

Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding

On Mon, 17 Feb 2025 at 16:20, Ajin Cherian wrote: > > On Mon, Feb 17, 2025 at 10:08 AM Peter Smith wrote: > > > > Hi Ajin. > > > > FYI - Patch set v13* no longer applies cleanly. Needs rebasing. > > > I've rebased the patch. I've also merged patch 1 into patch 2 as the > functionality of the chan

Re: Add -k/--link option to pg_combinebackup

Thanks for the review, Robert! I applied all of your suggestions. > I'm still not a fan of the changes to 010_links.pl; let's drop those. As discussed through a side chat, 010_links.pl is the new test file which ensures the hard links are created as expected in the output directory. I've removed

Re: Adding support for SSLKEYLOGFILE in the frontend

> On 20 Feb 2025, at 04:36, Abhishek Chanda wrote: > Please find attached a new version of this patch. I rebased on master, > added better error reporting and skipped the permissions check on > windows. Please let me know if this needs any changes. I tested this > locally using meson running all T

<    1   2