Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 286D01337BA3 for ; Mon, 4 Oct 2010 14:59:31 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 64400-02 for ; Mon, 4 Oct 2010 17:59:22 +0000 (UTC) X-Greylist: delayed 00:06:53.864913 by SQLgrey-1.7.6 Received: from mail-bw0-f46.google.com (mail-bw0-f46.google.com [209.85.214.46]) by mail.postgresql.org (Postfix) with ESMTP id 253221337BAC for ; Mon, 4 Oct 2010 14:59:21 -0300 (ADT) Received: by bwz11 with SMTP id 11so3819244bwz.19 for ; Mon, 04 Oct 2010 10:59:21 -0700 (PDT) Received: by 10.204.68.136 with SMTP id v8mr7243577bki.88.1286214746778; Mon, 04 Oct 2010 10:52:26 -0700 (PDT) Received: from Craig-Jamess-MacBook-Pro.local (wsip-70-167-124-126.sd.sd.cox.net [70.167.124.126]) by mx.google.com with ESMTPS id 24sm3982509bkr.19.2010.10.04.10.52.23 (version=SSLv3 cipher=RC4-MD5); Mon, 04 Oct 2010 10:52:24 -0700 (PDT) Message-ID: <4CAA1455.7070102@emolecules.com> Date: Mon, 04 Oct 2010 10:52:21 -0700 From: Craig James User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Default session timeout in PG? References: <1488581605.1434614.1286213760137.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> In-Reply-To: <1488581605.1434614.1286213760137.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/24 X-Sequence-Number: 35765 On 10/4/10 10:36 AM, Lou Picciano wrote: > (Think I've seen the answer to this already, but:) is there any 'innate', or > 'default' session timeout function built in to PG? > > We have certain clients who seem to timeout pretty frequently, while > others seem to never time out at all; before we start diagnosing networks, I want to be sure there's nothing we can do server-side to ameliorate/control the problem. We discovered the other day that a whole class of Netgear routers (designed for small businesses) contain a bug: they cut off all idle TCP/IP connections after 5 minutes, and there is no way to change this behavior. We threw them away. Craig