Re: Proposal: Conflict log history table for Logical Replication

Peter Smith <smithpb2250@gmail.com>

From: Peter Smith <smithpb2250@gmail.com>

To: Dilip Kumar <dilipbalaut@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, shveta malik <shveta.malik@gmail.com>, vignesh C <vignesh21@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-01-19T07:02:33Z

Lists: pgsql-hackers

Hi Dilip.

Thanks for the updates.

I checked the v23-0001 and v23-0002, and they LGTM.

I'll revisit at patch 0003 (docs) another time.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

Commits

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

Allow logical replication conflicts to be logged to a table.
- a5918fddf10d master landed
Avoid orphaned objects dependencies
- 2fbb21170e90 19 (unreleased) cited