Re: Proposal: Conflict log history table for Logical Replication

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>

To: Nisha Moond <nisha.moond412@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>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-07-06T07:44:27Z

Lists: pgsql-hackers

Attachments

0001-doc-Add-catalog-documentation-for-logical-replicatio.patch (application/octet-stream) patch 0001

On Fri, Jul 3, 2026 at 5:25 PM Nisha Moond <nisha.moond412@gmail.com> wrote:
>
> For the pushed patch (commit a5918fd), it seems we missed updating the
> pg_subscription catalog documentation for the two newly added columns:
>
> subconflictlogrelid | oid  |           | not null |
> subconflictlogdest  | text | C         | not null |
>
> Attached is a small patch for the same.

Yeah that make sense, also added a extra change suggested by Peter for
<firstterm> markup.

-- 
Regards,
Dilip Kumar
Google

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