Re: t help PostgreSQL server: FATAL 1: S

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Priya G <sreepriya(at)hotmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: t help PostgreSQL server: FATAL 1: S
Date: 2003-10-07 14:39:06
Message-ID: Pine.LNX.4.33.0310070836350.11210-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, 7 Oct 2003, Priya G wrote:

> I saw this error
> PostgreSQL server: FATAL 1: Sorry, too many clients already in
> /usr/share/php/phplib/db_pgsql.inc on line 49.
>  
> It seems like I have to increase the maximum connections in the postgresql.conf .Is that the
> right step to fix the problem..Also I am seeing lot of idle processess

Are you using pg_pconnect, or pg_connect?

pg_pconnect is not simple connection pooling, and can quickly run your
machine / apache server / postgresql server out of resources if improperly
configured.

It's best to reduce the max apache children to something like 30 or 40 and
increase postgresql to about 100 in this situation.

but for most people, persistant connects are no great advantage. On my
Dual PIII-750 server, I can create about 1,000 non-persistant connects a
second, while I can create 1,000,000 persistant connections a second.
Considering I can only server about 200 to 300 pages a second, the speed
of connection is pretty much below the level of noise on this system,
whether they be persistant or not.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Harald Fuchs 2003-10-07 14:40:21 Re: Checking Postgres Database
Previous Message scott.marlowe 2003-10-07 14:35:41 Re: Pgsql crashes frequently