Message-ID: <3DDBD5EE.4040804@intransa.com>
Date: Wed, 20 Nov 2002 10:35:26 -0800
From: Medi Montaseri <medi.montaseri@intransa.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
MIME-Version: 1.0
To: Francisco Reyes <lists@natserv.com>
Cc: pgsql General List <pgsql-general@postgresql.org>
Subject: Re: Closing inactive connections OR user connections limits
References: <20021120114805.C29739-100000@zoraida.natserv.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

In 7.2, you can run the vacuum in parallel with other database activities...
perhaps there is a way of reading from one of the pg_activity* or stats to
learn which connection is execessively idle and then go after it....

Francisco Reyes wrote:

>I have read on the archives some type of per user limit that will be
>available in 7.3, but what do I do in the meantime with a 7.2.X.
>
>Basically I came this morning to find a developer had a bug in a program
>and used up all the connections. Could I have safely killed those
>connections?
>
>I had to do a "pgsql stop -m fast" to free the connections, but I had some
>pending operations which now I will have to redo, not to mention the
>vacuum full failed last night because of the open connections.
>
>In all the archives I read there seems to be a negative view on timeouts.
>I think that after 4 hours of no activity, at least in my case, I
>definitely want those connections dead.
>
>In particular this is a reporting server and I delete/reload millions of
>records daily so anything which stops the vacuum full at night is a big
>problem for me.
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo@postgresql.org so that your
>message can get through to the mailing list cleanly
>  
>