Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

Peter Smith <smithpb2250@gmail.com>

View thread
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-20T21:20:33Z
Lists: pgsql-hackers 
On Tue, Jan 20, 2026 at 5:29 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Some review comments for v23-0003 (docs).
>
> ======
> doc/src/sgml/logical-replication.sgml
>
> 1. GENERAL.
>
> Mentioning those specific enum values of coflict_log_dest every time
> seemed overkill. In most cases you do really need to mention 'all' or
> 'log' ot 'table'. IMO the user should use the link to the
> 'conflict_log_destination' parameter to see that level of detail.
>

Oops. In my post above I wrote " In most cases you do really need to
mention...". That was a typo which was opposite of what I intended --
I meant " In most cases you do NOT really need to mention...".

======
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 →

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

  2. Avoid orphaned objects dependencies