From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Shay Rojansky <roji(at)roji(dot)org>, hlinnaka(at)iki(dot)fi, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Some 9.5beta2 backend processes not terminating properly? |
Date: | 2015-12-30 18:17:47 |
Message-ID: | 19926.1451499467@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-12-30 19:54:19 +0200, Shay Rojansky wrote:
>> wakeEvents is 8387808 and so is sock.
> Hm. That seems like an extremely weird value.
Probably just means the debugger is confused by optimized code.
> I think it's indicative of
> a bug in 80788a431e. Specifically secure_read/write's waitfor isn't
> necessarily set in the ssl case. Importantly not in the
> SSL_ERROR_SYSCALL case, which we're likely hitting here.
Hmm, that does look bogus ... and the Assert wouldn't fire in a non-assert
build. But waitfor would be zero if that was what was happening.
> Is this in a backend with ssl?
I thought we'd eliminated SSL already, or have I lost track of the
bidding? But I suspect you've identified a different bug.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shay Rojansky | 2015-12-30 18:18:52 | Re: Some 9.5beta2 backend processes not terminating properly? |
Previous Message | Andres Freund | 2015-12-30 18:15:07 | Re: Some 9.5beta2 backend processes not terminating properly? |