Re: Proposal: Conflict log history table for Logical Replication

From: Kedar Anavardekar <kedar(dot)anwardekar3(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(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-07-09 11:41:18
Message-ID: CAG0TzncAbF2fUpZBHUebRk4KeErxti0kvYm9C759JqZtn3p2yg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I rebased the remaining patches on top of HEAD. So far, I have run
> pgindent and completed the doc merge for 0001. The 0002 and 0003 are
> just rebased.
>

Hi Dilip,

I was testing on the master branch (commit
a5918fddf10d297c70f7ec9067e9177e0be6d520 -
"Allow logical replication conflicts to be logged to a table") for
basic CLT operations,
and ran into an issue I'd like to check with you.
I ran the SQL from the shell script and expected an insert conflict to
get logged in the CLT. I created the subscription as follows:

create subscription sub connection '...' publication pub
WITH(conflict_log_destination='table');
NOTICE: created conflict log table
"pg_conflict.pg_conflict_log_16414" for subscription "sub"
NOTICE: created replication slot "sub" on publisher
CREATE SUBSCRIPTION

However, I noticed that the conflicts are still being logged to the
log file rather than to pg_conflict.pg_conflict_log_16414.

Would you be able to let me know if my test setup was correct, or if
I'm missing a step somewhere? Any pointers would be much appreciated.

Thanks,
Kedar

Attachment Content-Type Size
CLT_test1.sh application/x-sh 2.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-07-09 12:10:57 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Ajin Cherian 2026-07-09 11:37:16 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade