Re: PGconn gets frozen ocassionally after select() timeout

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marek Peca <marek(at)duch(dot)cz>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PGconn gets frozen ocassionally after select() timeout
Date: 2009-11-13 17:45:10
Message-ID: 5255.1258134310@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Marek Peca <marek(at)duch(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marek Peca 2009-11-13 17:53:50 Re: PGconn gets frozen ocassionally after select() timeout
Previous Message Marek Peca 2009-11-13 17:19:49 Re: PGconn gets frozen ocassionally after select() timeout