Обсуждение: t help PostgreSQL server: FATAL 1: S

<div style="background-color:"><div>I saw this error </div><div><strong>PostgreSQL server: FATAL 1: Sorry, too many
clientsalready in /usr/share/php/phplib/db_pgsql.inc on line 49.</strong></div><div> </div><div>It seems like I have to
increasethe maximum connections in the postgresql.conf .Is that the right step to fix the problem..Also I am seeing lot
ofidle processess</div><div> </div></div><br clear="all" /><hr /><a href="http://g.msn.com/8HMBENUS/2755??PS=">Help
protectyour PC. Get a FREE computer virus scan online from McAfee.</a> 

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.