pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Neil Conway <neilc@samurai.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: 20 Nov 2002 12:54:46 -0500
Message-ID: <87ptt05dp5.fsf@mailbox.samurai.com> (raw)
In-Reply-To: <20021120114805.C29739-100000@zoraida.natserv.net>
References: <20021120114805.C29739-100000@zoraida.natserv.net>

Francisco Reyes <lists@natserv.com> writes:
> 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?

kill(1) the backends in question.

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

The superuser_reserved_connections feature we added for 7.3 should be
sufficient for this -- if the maintenance tasks are done as the
PostgreSQL superuser, there will be some reserved "slots" for them to
connect to.

Cheers,

Neil

-- 
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC




view thread (20+ messages)  latest in thread

Message-ID: <87ptt05dp5.fsf@mailbox.samurai.com>
Permalink:  ../87ptt05dp5.fsf@mailbox.samurai.com/
Also on:    postgresql.org/message-id/87ptt05dp5.fsf@mailbox.samurai.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: neilc@samurai.com, lists@natserv.com, pgsql-general@postgresql.org
  Subject: Re: Closing inactive connections OR user connections limits
  In-Reply-To: <87ptt05dp5.fsf@mailbox.samurai.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