Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D25BB9FB306 for ; Mon, 19 Mar 2007 18:45:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 87377-03 for ; Mon, 19 Mar 2007 18:45:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by postgresql.org (Postfix) with ESMTP id EEDD79FB301 for ; Mon, 19 Mar 2007 18:45:03 -0300 (ADT) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 55FD7207D36; Mon, 19 Mar 2007 17:45:00 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Mon, 19 Mar 2007 17:45:00 -0400 X-Sasl-enc: p+X+casmfi35Cug86XFcvxCOJ0JKaPCXyo5zQiNdet2J 1174340702 Received: from [192.168.0.100] (h-72-245-22-122.snfccasy.covad.net [72.245.22.122]) by mail.messagingengine.com (Postfix) with ESMTP id D0B6F181B1; Mon, 19 Mar 2007 17:45:01 -0400 (EDT) Message-ID: <45FF0470.2050403@augustz.com> Date: Mon, 19 Mar 2007 14:45:20 -0700 From: August Zajonc User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Ted Byers CC: pgsql-admin@postgresql.org Subject: Re: [Bulk] Re: Disconnecting non active (IDLE ) users References: <55c095e90702280801q484b75d8v3833a18c5d5a5c16@mail.gmail.com> <030c01c75b5e$0de7ffb0$6401a8c0@RnDworkstation> In-Reply-To: <030c01c75b5e$0de7ffb0$6401a8c0@RnDworkstation> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/123 X-Sequence-Number: 24947 Ted Byers wrote: [snip] > It is outrageously unethical, IMHO, for a programmer, or group thereof, > to refuse to fix a problem that has arisen from how their targetted > users use their application. Let's save the determination of outrageous behavior for others and see if we can help the user fix their problem. Two suggestions: Pgpool Change keepalive settings in kernel if the machine is only used for postgresql. If you disable keepalives, at some point the kernel will likely drop the connection. Postgresql turns keepalives on by default (which is usually a good thing). Your apps should login transparently though and know how to handle this issue. Prompting users repeatedly to login can be frustrating, the usual question is how to keep a connection open longer :) I'm not sure that postgresql would itself implement a timeout feature... Good luck. - August