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 CAA4eK1K38QO-T19WKtdm5FgfyW-e-ZX6uT9yuJuteNAzt=xcNg@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: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL
List pgsql-hackers
On Wed, May 20, 2026 at 11:01 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> Amit, Vignesh,
>
> A part of 007 patch is about preserving subscription-oid. Another
> thread (origin migration) also needs the same logic as per discussion
> at [1]. And there was a old thread which already attempted preserving
> subscription-oid at [2], but the idea was rejected at that time. Why
> don't we attempt to resume the same thread ([2]) and implement
> preserving subscription-oid as a separate thread as we now have
> multiple dependencies on it? Thoughts?
>

Agreed, but I think we can move the discussion/review to a separate
thread. However, at this stage, we can make initial patches ready and
then move to it.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: "Jonathan Gonzalez V."
Date:
Subject: Re: splitting pg_resetwal output strings
Next
From: Xuneng Zhou
Date:
Subject: Re: Fix pg_stat_wal_receiver to show CONNECTING status