Re: Proposal: Conflict log history table for Logical Replication

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Zhijie Hou <houzhijie22(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, saurabh singh <saurabh(dot)singh214(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shvetamalik(at)gmail(dot)com>
Subject: Re: Proposal: Conflict log history table for Logical Replication
Date: 2026-11-04 07:08:25
Message-ID: CAHut+PveJVZ-fhR6TpZjmMV2FnpwtSK3_iBjj-=GvF_DtmrGQA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The docs already say:

+ <para>
+ The apply worker's <xref linkend="guc-datestyle"/>,
+ <xref linkend="guc-intervalstyle"/>,
+ <xref linkend="guc-extra-float-digits"/>,
+ <xref linkend="guc-bytea-output"/> and
+ <xref linkend="guc-quote-all-identifiers"/> settings can affect how a
+ key value is written. If these settings differ between conflicts, the
+ same key can be recorded in different forms, and comparing the recorded
+ text may miss some of them. For settings that affect only the

~~~

I think the GUC timezone is yet another setting that can affect how a
key value is written, so it should be similary mentioned.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-11-04 07:08:56 Re: [PATCH v1] psql: Do not complete JSON format for COPY FROM
Previous Message Chao Li 2026-11-04 07:05:52 Re: [PATCH v1] psql: Do not complete HEADER MATCH for COPY TO