| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Timeout failure in 019_replslot_limit.pl |
| Date: | 2021-09-27 06:43:52 |
| Message-ID: | YVFoKJoIRN43qNAU@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2021-09-27 06:45:50 | RE: Added schema level support for publication. |
| Previous Message | Amit Kapila | 2021-09-27 06:23:07 | Re: Timeout failure in 019_replslot_limit.pl |