| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, 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: | 2016-01-02 17:22:23 |
| Message-ID: | 20160102172223.3q5fxll65hvsztvr@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-01-02 15:40:03 +0100, Andres Freund wrote:
> If FD_CLOSE is indeed edge and not level triggered - which imo would be
> supremely insane - we'd be in trouble. It'd explain why some failures
> are noticed and others not.
I wonder if the FD_CLOSE and FD_WRITE being edge-triggered is the actual
root cause for:
/*
* Just a workaround of unknown locking problem with writing in UDP socket
* under high load: Client's pgsql backend sleeps infinitely in
* WaitForMultipleObjectsEx, pgstat process sleeps in pgwin32_select().
* So, we will wait with small timeout(0.1 sec) and if socket is still
* blocked, try WSASend (see comments in pgwin32_select) and wait again.
*/
if ((what & FD_WRITE) && isUDP)
in pgwin32_waitforsinglesocket().
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-01-02 17:28:10 | Re: Some 9.5beta2 backend processes not terminating properly? |
| Previous Message | Bruce Momjian | 2016-01-02 17:00:36 | Re: Welcome to 2016, time to run src/tools/copyright.pl |