Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

Shlok Kyal <shlok.kyal.oss@gmail.com>

View thread
From: Shlok Kyal <shlok.kyal.oss@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: shveta malik <shveta.malik@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-07-03T05:32:46Z
Lists: pgsql-hackers 
> Yeah, IMHO once we fix [1] this issue should be automatically resolved.
>
> [1] https://www.postgresql.org/message-id/akZUpiDa1UfmzYxL%40bdtpg
>
Yes, I tested the CLT patches on top of patch provided by Bertrand in
[1]. And I verified that it fixes the Assertion issue.
[1]: https://www.postgresql.org/message-id/akZUpiDa1UfmzYxL%40bdtpg

Thanks,
Shlok Kyal

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