Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T4N5p-00087K-15 for pgsql-bugs@postgresql.org; Thu, 23 Aug 2012 02:24:21 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T4N5o-00069g-2S for pgsql-bugs@postgresql.org; Thu, 23 Aug 2012 02:24:20 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q7N2OBYp028584; Wed, 22 Aug 2012 22:24:11 -0400 (EDT) From: Tom Lane To: Robert Haas cc: Alvaro Herrera , Luke Koops , Pg Bugs Subject: Re: BUG #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram In-reply-to: References: <200907311459.n6VExuSa036743@wwwmaster.postgresql.org> <1410.1344363743@sss.pgh.pa.us> <1345576064-sup-7145@alvh.no-ip.org> <9323.1345581034@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Tue, 21 Aug 2012 22:48:58 -0400" Date: Wed, 22 Aug 2012 22:24:11 -0400 Message-ID: <28583.1345688651@sss.pgh.pa.us> X-Pg-Spam-Score: -2.1 (--) X-Archive-Number: 201208/170 X-Sequence-Number: 33894 Robert Haas writes: > On Tue, Aug 21, 2012 at 4:30 PM, Tom Lane wrote: >> Meanwhile, back at the ranch: I'm fine with applying that patch now that >> it's had some field testing. > Attached is a version that applies OK to 9.1, after resolving some > conflicts. Review appreciated. It wasn't exactly clear to me how to > handle the ereport/elog calls. It looks sane to me in a quick once-over (bearing in mind I can't test it). What's bothering you about the ereport calls? > What to do pre-9.1 is a bit less clear to me, as the latch machinery > doesn't exist at all in those versions. Some of the fixes can > probably still be pulled out and applied, though. Presumably the changes in win32/socket.c could still be applied; but on the other hand it's not clear there's so much need for them pre-9.1. IIRC most of the point of this patch was to eliminate the tug-of-war over the socket's event attachment between socket.c and win32_latch.c, so maybe there's not a bug pre-9.1. regards, tom lane