Am 09.06.2010 16:37, schrieb Tom Lane:
Marinos Yannikos writes:
It seems that poll() never receives a connection closed notification under Linux
(https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008335.html -
very old report,
"very old report" is right. What makes you think
=?ISO-8859-1?Q?bj=F6rn_lundin?= writes:
> On 9 Juni, 16:37, t...@sss.pgh.pa.us (Tom Lane) wrote:
>> "very old report" is right. What makes you think that has anything to
>> do with modern kernel versions?
> Interesting. The bug report includes a short code snippet which
> compiles to a c program
Excerpts from björn lundin's message of mié jun 09 16:17:57 -0400 2010:
> On 9 Juni, 16:37, t...@sss.pgh.pa.us (Tom Lane) wrote:
> > Marinos Yannikos writes:
> > > It seems that poll() never receives a connection closed notification
> > > under Linux
> > > (https://lists.linux-foundation.org/pipe
On 9 Juni, 16:37, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Marinos Yannikos writes:
> > It seems that poll() never receives a connection closed notification under
> > Linux
> > (https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008...-
> > very old report,
>
> "very old report" is r
Marinos Yannikos writes:
> It seems that poll() never receives a connection closed notification under
> Linux
> (https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008335.html
> -
> very old report,
"very old report" is right. What makes you think that has anything to
do with
Hi,
we had a kernel panic crashing our DB server today and all libpq clients (C and
Perl clients) got stuck in poll() for hours even after the server was back up,
i.e. longer than the tcp timeout should be:
#0 0x2b2283b31c8f in poll () from /lib/libc.so.6
#1 0x2b228446f4af in PQmble
