Re: Add an option to skip loading missing publication to avoid logical replication failure - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Add an option to skip loading missing publication to avoid logical replication failure
Date
Msg-id CAA4eK1Lys6m6OHmVYzfzbXfXEOekV=RtYS9PJa+3wWmD813a=w@mail.gmail.com
Whole thread Raw
In response to Re: Add an option to skip loading missing publication to avoid logical replication failure  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, May 6, 2025 at 5:17 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Tue, May 6, 2025 at 3:33 PM Xuneng Zhou <xunengzhou@gmail.com> wrote:
> >
> > A clear benefit of addressing this in code is to ensure that the user sees the log message, which can be valuable
fortrouble-shooting—even under race conditions. 
> >
>
> I don't think we can take that guarantee because if the Insert is
> concurrent or slightly before the Alter Subscription command, then
> there won't be a guarantee that users will see the skipped LOG
> message.
>

I am planning to proceed with the test-fix proposed by Vignesh [1]
early next week unless we want to discuss more on this issue.

[1] - https://www.postgresql.org/message-id/CALDaNm3TH3J8fwj%2BNcdjdN8DZCdrnmm1kzBsHBW2nkN%2Bh6up3A%40mail.gmail.com

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Fix slot synchronization with two_phase decoding enabled
Next
From: Tomas Vondra
Date:
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree