From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Trevor Talbot" <quension(at)gmail(dot)com>, "Richard Huxton" <dev(at)archonet(dot)com>, "Steve Crawford" <scrawford(at)pinpointresearch(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql hanging |
Date: | 2007-09-05 20:53:42 |
Message-ID: | dcc563d10709051353w2320464eob0d4ecc589ff4d88@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/5/07, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Wed, Sep 05, 2007 at 10:44:20AM -0700, Trevor Talbot wrote:
> > Unless psql is turning on keepalive or similar, or the OS is forcing
> > it on by default, there are no timeouts for idle TCP connections. If
> > the command was transported to the server successfully and psql was
> > just waiting for a result, the connection is idle and nothing will
> > happen if the server end suddenly goes away.
>
> Well, any TCP implementation has to support keepalives and generally
> they are turned on by default, but to something like 2 days. Anything
> months old must be caused by something else (overzealous firewall
> dropping the RST packets in response to the keepalives?).
The default for RHEL3 and 4 is 2 hours.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Trutwin | 2007-09-05 21:17:22 | Querying database for table pk - better way? |
Previous Message | Rodrigo De León | 2007-09-05 20:44:03 | Re: now() vs current_user |