Re: Proposal: Conflict log history table for Logical Replication

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal: Conflict log history table for Logical Replication
Date: 2026-01-20 21:20:33
Message-ID: CAHut+PteQmk6w=AV9qbnYaRZf5bo1jeTW0=XMjFUpWH0+UyZqw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 20, 2026 at 5:29 PM Peter Smith <smithpb2250(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Fittl 2026-01-20 21:27:05 Re: pg_stat_statements: Fix nested tracking for implicitly closed cursors
Previous Message Zsolt Parragi 2026-01-20 21:13:53 Re: [oauth] Stabilize the libpq-oauth ABI (and allow alternative implementations?)