On Tue, 5 Aug 2003, Lynna Landstreet wrote: > on 8/5/03 3:07 PM, scott.marlowe at scott.marlowe@xxxxxxx wrote: > > > On Tue, 5 Aug 2003, Lynna Landstreet wrote: > > > >> But hey, come to think of it, maybe I could turn the pg_connect into a > >> pg_pconnect and just have it check to see if $db already exists before > >> connecting - that way there'd be only one connection per site visit! Cool, > >> your question gave me a new idea... :-) > > > > Be VERY wary of persistant connections. They are fraught with danger and > > can cause your server to present the "too many connections" error message > > after being up for a while. <rest snipped> > > Hmmm, OK. I didn't realize they didn't time out. Maybe it's best to leave it > the way it is now, with just one pg_connect being called in the head of each > document. Thanks. they can be set to, but it's by request, not over time. max requests per child or some such setting. Setting it low enough helps prevent certain problems. It's just that the default settings for apache/php/postgresql are all designed to make your box go kaboom if you use persistant connects. :-)
