Re: Failure of subscription tests with topminnow
От | Ajin Cherian |
---|---|
Тема | Re: Failure of subscription tests with topminnow |
Дата | |
Msg-id | CAFPTHDZdGvoH5cn0TFqGBF1a7Tds5rK4wAR3cLOh89rLp=CCLQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Failure of subscription tests with topminnow (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Failure of subscription tests with topminnow
|
Список | pgsql-hackers |
On Wed, Aug 25, 2021 at 4:22 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Wed, Aug 25, 2021 at 8:00 AM Ajin Cherian <itsajin@gmail.com> wrote: > > > > On Tue, Aug 24, 2021 at 11:12 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > But will poll function still poll or exit? Have you tried that? > > > > I have forced that condition with a changed query and found that the > > poll will not exit in case of a NULL return. > > > > What if the query in a poll is fired just before we get an error > "tap_sub ERROR: replication slot "tap_sub" is active for PID 16336"? > Won't at that stage both old and new walsender's are present, so the > query might return true. You can check that via debugger by stopping > just before this error occurs and then check pg_stat_replication view. If this error happens then the PID is NOT updated as the pid in the Replication slot. I have checked this and explained this in my first email itself regards, Ajin Cherian Fujitsu Australia
В списке pgsql-hackers по дате отправления: