Re: What is wrong with pg_pconnect() ?

As Rod pointed out, you likely aren't having dead apache children, just 
too many.

IF you must have pconnects in your code, then you need to configure your 
apache server and postgresql server so that the postgresql server can 
spawn more children than the apache server.

Set MaxClients in httpd.conf to something MUCH lower than the default 
of 150.  Usually 20 to 50 will be plenty.  Restart apache.

Then, set postgresql to handle at least 2x as many backends as with the 
max_connections setting and restart it.

Now, you should be able to handle pconnects.  

My personal testing has shown my dual PIII-750 (being retired at the end 
of the month) can handle about 1,000 to 10,000 pg_connects a second, and 
about 100,000 to 1,000,000 pg_pconnects a second.  Since the average page 
build / delivery time on our intranet server is around 0.5 to 1.5 seconds, 
the speed of connections is pretty much noise.  We have templating, 
database accesses, and httpd authentication via LDAP on each page, and the 
biggest eater of CPU time is the httpd->LDAP authentication, followed by 
the templating, followed by the database layer.  I.e. Postgresql and its 
connections are the least of our worries. :-0


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
      message can get through to the mailing list cleanly