Re: Add an option to skip loading missing publication to avoid logical replication failure

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, tgl(at)sss(dot)pgh(dot)pa(dot)us, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add an option to skip loading missing publication to avoid logical replication failure
Date: 2025-05-10 11:45:22
Message-ID: CAA4eK1Lys6m6OHmVYzfzbXfXEOekV=RtYS9PJa+3wWmD813a=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 6, 2025 at 5:17 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Tue, May 6, 2025 at 3:33 PM Xuneng Zhou <xunengzhou(at)gmail(dot)com> wrote:
> >
> > A clear benefit of addressing this in code is to ensure that the user sees the log message, which can be valuable for trouble-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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ikedarintarof 2025-05-10 13:45:31 Suggestion to add --continue-client-on-abort option to pgbench
Previous Message Amit Kapila 2025-05-10 11:29:20 Re: Fix slot synchronization with two_phase decoding enabled