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

From shveta malik
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAJpy0uCP0QepMZBJhqhzvp4tZ9X3_k32S9Q+EG9tmpaY3=GUTA@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (Amit Kapila <amit.kapila16@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Deadlock detector fails to activate on a hot standby replica
Next
From: Fujii Masao
Date:
Subject: Re: bump minimum supported version of psql and pg_{dump,dumpall,upgrade} to v10