Re: PGconn gets frozen ocassionally after select() timeout - Mailing list pgsql-general

From Tom Lane
Subject Re: PGconn gets frozen ocassionally after select() timeout
Date
Msg-id 5255.1258134310@sss.pgh.pa.us
Whole thread Raw
In response to Re: PGconn gets frozen ocassionally after select() timeout  (Marek Peca <marek@duch.cz>)
Responses Re: PGconn gets frozen ocassionally after select() timeout  (Marek Peca <marek@duch.cz>)
List pgsql-general
Marek Peca <marek@duch.cz> writes:
>> In any case, that complaint should be directed to your kernel vendor
>> not us.  We do not control how long the TCP stack waits before declaring
>> the connection dead.

> Well, this is what I wanted to hear. So if I call PQstatus() or PQexec(),
> the libpq sends some data to the TCP pipe, and you expect, that my broken
> underlying TCP/IP subsystem pretends, that the connection is OK and the
> data have been sent. Right?

Well, if you *never* get a failure, then yeah I think you have a broken
TCP stack.  The default timeouts on this sort of thing are annoyingly
long, but they aren't infinite.

            regards, tom lane

pgsql-general by date:

Previous
From: Marek Peca
Date:
Subject: Re: PGconn gets frozen ocassionally after select() timeout
Next
From: Marek Peca
Date:
Subject: Re: PGconn gets frozen ocassionally after select() timeout