Re: Timeout failure in 019_replslot_limit.pl

Поиск
Список
Период
Сортировка
Искать
От
Michael Paquier
Тема
Re: Timeout failure in 019_replslot_limit.pl
Дата
Msg-id
YVFoKJoIRN43qNAU@paquier.xyz
Ответ на
Список
Дерево обсуждения
Timeout failure in 019_replslot_limit.pl Michael Paquier <michael@paquier.xyz>
Re: Timeout failure in 019_replslot_limit.pl Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Timeout failure in 019_replslot_limit.pl Tom Lane <tgl@sss.pgh.pa.us>
Re: Timeout failure in 019_replslot_limit.pl Michael Paquier <michael@paquier.xyz>
Re: Timeout failure in 019_replslot_limit.pl Kyotaro Horiguchi <horikyota.ntt@gmail.com>
On Mon, Sep 27, 2021 at 11:53:07AM +0530, Amit Kapila wrote:
> So, it seems on your machine it has passed  the following condition in
> secure_write:
> if (n < 0 && !port->noblock && (errno == EWOULDBLOCK || errno == EAGAIN))

Yep.

> If so, this indicates write failure which seems odd to me and probably
> something machine-specific or maybe some different settings in your
> build or machine. BTW, if SSL or GSS is enabled that might have caused
> it in some way. I think the best way is to debug the secure_write
> during this occurrence.

Yeah, but we don't use any of them in the context of this test, so
this is something on a simple send(), no?  Hmm.  That would not be the
first issue we see with macos these days with interrupted syscalls...
And actually in this stack I can see that errno gets set to EINTR.
--
Michael
В списке pgsql-hackers по дате отправления
От: Amit Kapila
Дата:
От: houzj.fnst@fujitsu.com
Дата:
FAQ