Re: Why is src/test/modules/committs/t/002_standby.pl flaky?
От | Thomas Munro |
---|---|
Тема | Re: Why is src/test/modules/committs/t/002_standby.pl flaky? |
Дата | |
Msg-id | CA+hUKGKaq1Nv79sQptmDCgJc2tGUKogW-YxAyTyF1WvJerR0RQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Why is src/test/modules/committs/t/002_standby.pl flaky? (Alexander Lakhin <exclusion@gmail.com>) |
Ответы |
Re: Why is src/test/modules/committs/t/002_standby.pl flaky?
|
Список | pgsql-hackers |
On Mon, Jan 10, 2022 at 8:00 PM Alexander Lakhin <exclusion@gmail.com> wrote: > The libpqrcv_PQgetResult function, in turn, invokes WaitLatchOrSocket() > where WaitEvents are defined locally, and the closed flag set on the > first invocation but expected to be checked on second. D'oh, right. There's also a WaitLatchOrSocket call in walreceiver.c. We'd need a long-lived WaitEventSet common across all of these sites, which is hard here (because the socket might change under you, as discussed in other threads that introduced long lived WaitEventSets to other places but not here). /me wonders if it's possible that graceful FD_CLOSE is reported only once, but abortive/error FD_CLOSE is reported multiple times...
В списке pgsql-hackers по дате отправления: