Skip site navigation (1) Skip section navigation (2)

Re: idle connection timeout ...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andrew Sullivan <andrew(at)libertyrms(dot)info>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: idle connection timeout ...
Date: 2002-10-25 19:02:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Sullivan wrote:
> On Fri, Oct 25, 2002 at 11:02:48AM -0400, Tom Lane wrote:
> > So?  If it hits the installation-wide limit, you'll have the same
> > problem; and at that point the (presumably runaway) app would have
> > sucked up all the connections, denying service to other apps using other
> > databases.  I think Marc's point here is to limit his exposure to
> > misbehavior of any one client app, in a database server that is serving
> > multiple clients using multiple databases.
> That would indeed be a useful item.  The only way to avoid such
> exposure right now is to run another back end.

Added to TODO:

	* Allow limits on per-db/user connections

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Mike BenoitDate: 2002-10-25 19:16:50
Subject: Re: idle connection timeout ...
Previous:From: Andrew SullivanDate: 2002-10-25 18:47:01
Subject: Re: idle connection timeout ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group