Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

Zsolt Parragi <zsolt.parragi@percona.com>

View thread
From: Zsolt Parragi <zsolt.parragi@percona.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2026-06-24T19:31:33Z
Lists: pgsql-hackers 
Hello

+my $locker = $node_sub->background_psql('postgres');
+$locker->query_until(qr/locker_ready/, qq{
+	\\echo locker_ready
+	BEGIN;
+	TRUNCATE $clt;
+});

This seems unstable to me: can't query_until return as soon as
"locker_ready" appears in the output, before the begin; truncate?

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow logical replication conflicts to be logged to a table.

  2. Avoid orphaned objects dependencies