Re: Selectively invalidate caches in pgoutput module
От | Amit Kapila |
---|---|
Тема | Re: Selectively invalidate caches in pgoutput module |
Дата | |
Msg-id | CAA4eK1LnDhA+x5LY8WY-Un6aG=K9mvXMB0FTrf17hiAmkUNUdA@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Selectively invalidate caches in pgoutput module ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>) |
Ответы |
RE: Selectively invalidate caches in pgoutput module
|
Список | pgsql-hackers |
On Fri, Mar 28, 2025 at 6:03 AM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Dear Andres, > > > I think the new tests just failed in CI: > > https://cirrus-ci.com/task/5602950271205376?logs=test_world#L268 > > Thanks for reporting, I'll look into it. > 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. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: