I wrote:
> While testing this I discovered a pre-existing bug in the Unix
> implementation of WaitLatchOrSocket: EOF on the socket is reported as
> POLLHUP not POLLIN (at least on my Linux box), which results in
> WaitLatchOrSocket going into an infinite loop, because poll() returns
> immediately b
Andrew Dunstan writes:
>> On 05/12/2012 03:36 PM, Tom Lane wrote:
> ... I do not however have the ability
> to test the Windows side of it, so it'd be nice if someone would check
> that that still works (particularly, that it shuts down cleanly).
> Everything looks kosher on my Windows machine (t
On 05/12/2012 04:00 PM, Andrew Dunstan wrote:
On 05/12/2012 03:36 PM, Tom Lane wrote:
I noticed a large oversight in our efforts to reduce the server's idle
wakeup frequency: if you've got logging_collector turned on, the
syslogger process will wake up once a second, whether it has anything
On 05/12/2012 03:36 PM, Tom Lane wrote:
I noticed a large oversight in our efforts to reduce the server's idle
wakeup frequency: if you've got logging_collector turned on, the
syslogger process will wake up once a second, whether it has anything
to do or not. But the only reasons it has for wa
I noticed a large oversight in our efforts to reduce the server's idle
wakeup frequency: if you've got logging_collector turned on, the
syslogger process will wake up once a second, whether it has anything
to do or not. But the only reasons it has for waking up are signals,
data arrival, and time-
