From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Rare SSL failures on eelpout |
Date: | 2019-03-05 14:33:08 |
Message-ID: | 17851.1551796388@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> BTW, I went looking for other failures on the buildfarm I noticed that
> even for eelpout it's only happening on master and REL_11_STABLE:
Yeah, I'd noticed that.
> Disappointingly, that turned out to be just because 10 and earlier
> didn't care what the error message said.
That is, you can reproduce the failure on old branches? That lets
out a half-theory I'd had, which was that Andres' changes to make
the backend always run its socket in nonblock mode had had something
to do with it. (Those changes do represent a plausible reason why
SSL_shutdown might be returning WANT_READ/WANT_WRITE; but I'm not
in a hurry to add such code without evidence that it actually
happens and something useful would change if we retry.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-03-05 14:35:14 | Re: proposal: new polymorphic types - commontype and commontypearray |
Previous Message | Pavel Stehule | 2019-03-05 14:10:44 | Re: Re: proposal: new polymorphic types - commontype and commontypearray |