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

From Amit Kapila
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAA4eK1Led6RtGuuaLu_Hy8Qz+1WFRTuEoi086U5SXjKEnaFrjQ@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Proposal: Conflict log history table for Logical Replication
List pgsql-hackers
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.

--
With Regards,
Amit Kapila.

Attachment

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: [PATCH] Document wal_compression=on
Next
From: Chengpeng Yan
Date:
Subject: Re: Fix HAVING-to-WHERE pushdown with mismatched operator families