Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

shveta malik <shveta.malik@gmail.com>

View thread
From: shveta malik <shveta.malik@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, vignesh C <vignesh21@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, shveta malik <shveta.malik@gmail.com>
Date: 2026-06-30T03:30:09Z
Lists: pgsql-hackers 
On Mon, Jun 29, 2026 at 4:13 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Jun 29, 2026 at 2:21 PM shveta malik <shveta.malik@gmail.com> wrote:
> >
> > IMO, we should silently skip CLT by expanding the check in
> > AlterTableMoveAll() similar to system-tables.
> >
>
> Agreed, otherwise, it will break the entire bulk operation. I have
> tried to fix this in the attached and modified the required tests. I
> think we should merge 0001 and 0002, and move these tablespace related
> tests to 0001.
>

Thanks. The fix looks good.

thanks
Shveta

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow logical replication conflicts to be logged to a table.

  2. Avoid orphaned objects dependencies