Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id B9AF91337BC6 for ; Mon, 4 Oct 2010 15:47:45 -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 04729-01 for ; Mon, 4 Oct 2010 18:47:38 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 1AD7C1337B92 for ; Mon, 4 Oct 2010 15:47:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o94IlYG5005297; Mon, 4 Oct 2010 14:47:35 -0400 (EDT) To: Lou Picciano cc: pgsql-admin Subject: Re: Default session timeout in PG? In-reply-to: <1488581605.1434614.1286213760137.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> References: <1488581605.1434614.1286213760137.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Comments: In-reply-to Lou Picciano message dated "Mon, 04 Oct 2010 17:36:00 -0000" Date: Mon, 04 Oct 2010 14:47:34 -0400 Message-ID: <5296.1286218054@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/25 X-Sequence-Number: 35766 Lou Picciano writes: > 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. > If I recall correctly, PG does not, by default, timeout its connections, right? PG does not have a session timeout of any sort, default or otherwise. I think you're looking at a network infrastructure issue. If there are any NAT routers between those clients and the database, that would be the place to look first. regards, tom lane