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-06 11:47:37
Message-ID: CAA4eK1LGASeNZjQspR4SKLvGAkvWTSWwQYZorwm3rhhYf+1KBA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2025-05-06 12:29:27 Re: 2025-05-08 release announcement draft
Previous Message Laurenz Albe 2025-05-06 11:28:18 Re: A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a explosive replication lag. Oh my.