Re: Proposal: Conflict log history table for Logical Replication - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAHut+PteQmk6w=AV9qbnYaRZf5bo1jeTW0=XMjFUpWH0+UyZqw@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Conflict log history table for Logical Replication  (Peter Smith <smithpb2250@gmail.com>)
List 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.



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: [oauth] Stabilize the libpq-oauth ABI (and allow alternative implementations?)
Next
From: Lukas Fittl
Date:
Subject: Re: pg_stat_statements: Fix nested tracking for implicitly closed cursors