Re: Selectively invalidate caches in pgoutput module - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Selectively invalidate caches in pgoutput module
Date
Msg-id CAA4eK1L4Uofc=6KXNW24Dwjd6UMP2W9WNJnwYrkqPXkAAxq-jw@mail.gmail.com
Whole thread Raw
In response to RE: Selectively invalidate caches in pgoutput module  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
On Fri, Mar 28, 2025 at 10:46 AM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> > The problem here is that after ALTER SUBSCRIPTION tap_sub SET
> > PUBLICATION ..., we didn't wait for the new walsender on publisher to
> > start. We must use wait_for_subscription_sync both after the "CREATE
> > SUBSCRIPTION ..." and the "ALTER SUBSCRIPTION ..." commands and keep
> > copy_data=true to ensure the initial replication is setup between
> > publisher and subscriber. This is how we use these commands at other
> > places.
>
> Agreed. PSA the patch to fix the issue.
>

Pushed after slight modification.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Assert failure in base_yyparse
Next
From: Amit Kapila
Date:
Subject: Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.