pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Medi Montaseri <medi.montaseri@intransa.com>
To: Francisco Reyes <lists@natserv.com>
Cc: pgsql General List <pgsql-general@postgresql.org>
Subject: Re: Closing inactive connections OR user connections limits
Date: Wed, 20 Nov 2002 10:35:26 -0800
Message-ID: <3DDBD5EE.4040804@intransa.com> (raw)
References: <20021120114805.C29739-100000@zoraida.natserv.net>

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
>  
>






view thread (20+ messages)  latest in thread

Message-ID: <3DDBD5EE.4040804@intransa.com>
Permalink:  ../3DDBD5EE.4040804@intransa.com/
Also on:    postgresql.org/message-id/3DDBD5EE.4040804@intransa.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: medi.montaseri@intransa.com, lists@natserv.com, pgsql-general@postgresql.org
  Subject: Re: Closing inactive connections OR user connections limits
  In-Reply-To: <3DDBD5EE.4040804@intransa.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox