| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Shay Rojansky <roji(at)roji(dot)org>, hlinnaka(at)iki(dot)fi |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Some 9.5beta2 backend processes not terminating properly? |
| Date: | 2015-12-30 18:07:08 |
| Message-ID: | 20151230180708.bcwxvu37t6jretdb@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-12-30 19:54:19 +0200, Shay Rojansky wrote:
> >
> > Things that'd be interesting:
> > 1) what are the arguments passed to WaitLatchOrSocket(), most
> > importantly wakeEvents and sock
> >
>
> wakeEvents is 8387808 and so is sock.
Hm. That seems like an extremely weird value. 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.
Is this in a backend with ssl?
If you go up one frame, what value does port->sock have?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shay Rojansky | 2015-12-30 18:12:07 | Re: Some 9.5beta2 backend processes not terminating properly? |
| Previous Message | Shay Rojansky | 2015-12-30 18:02:29 | Re: Some 9.5beta2 backend processes not terminating properly? |