From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Copeland <greg(at)CopelandConsulting(dot)Net>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: idle connection timeout ... |
Date: | 2002-10-25 15:52:36 |
Message-ID: | 200210251552.g9PFqaP27140@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Basically, total connections is to be set larger than you think you will
> > ever need, while you expect per-db to be hit, and if something keeps
> > trying to connect and failing, we may get very bad connection
> > performance for other backends.
>
> Hmm, I see your point. A per-db limit *could* be useful even if it's
> set high enough that you don't expect it to be hit ... but most likely
> people would try to use it in a way that it wouldn't be very efficient
> compared to a client-side solution.
The only way to do it would be, after a few hits of the limit, to start
delaying the connection rejections so you don't get hammered. It could
be done, but even then, I am not sure if it would be optimal.
--
Bruce Momjian | http://candle.pha.pa.us
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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2002-10-25 16:07:10 | Re: idle connection timeout ... |
Previous Message | Tom Lane | 2002-10-25 15:46:47 | Re: idle connection timeout ... |