Re: Proposal: Conflict log history table for Logical Replication

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>
Subject: Re: Proposal: Conflict log history table for Logical Replication
Date: 2026-10-16 21:41:07
Message-ID: CAN4CZFNaWLs6rAOX3KNzgQ0ci-6PB+mWJNj_6_F-O_vomb8Euw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> +1 for b. Offhand, I don't see any problem with it but if we discover
> anything during our implementation, we can revisit this decision.

The attached patch implements option B from my previous email (DROP
SUBSCRIPTION honoring RESTRICT for the conflict log table)

Attachment Content-Type Size
nocfbot-0001-Honor-RESTRICT-when-dropping-a-subscription-s-con.patch application/octet-stream 9.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-10-16 21:44:35 Re: pg_*_advice: tsv load failure, etc.
Previous Message Robert Haas 2026-10-16 21:26:42 Re: pg_*_advice: tsv load failure, etc.