From: | will trillich <will(at)serensoft(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: too many users for postgresql? :) |
Date: | 2003-01-27 16:50:35 |
Message-ID: | 20030127165035.GA12959@mail.serensoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 27, 2003 at 08:57:39AM -0500, Lamar Owen wrote:
> > will trillich wrote:
> > > Warning: pg_connect() unable to connect to PostgreSQL
> > > server: FATAL 1: Sorry, too many clients already in
> > > /usr/local/www/www.postgresql.org/idocs/opendb.php on line 3
> > > Unable to access database
> This is one of the biggest advantages to the pooled model of
> AOLserver. If you have the number of connections to the
> database set equal to the number of connection threads, you
> can never get this sort of message. The webserver will refuse
> the connection first -- which is probably a better thing to
> do, rather than give such a damaging ('What? PostgreSQL can't
> scale to the load of its own server?') error message.
a MUCH better thing. :)
--
There are 10 kinds of people:
ones that get binary, and ones that don't.
will(at)serensoft(dot)com
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!
Looking for a firewall? Do you think smoothwall sucks? You're
probably right... Try the folks at http://clarkconnect.org/ !
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-01-27 16:51:21 | Re: Function returns mutliple rows - HELP |
Previous Message | juleni | 2003-01-27 16:46:42 | Function returns mutliple rows - HELP |