Clinging to sanity, [EMAIL PROTECTED] (Jón Ragnarsson) mumbled into her beard: > I am writing a website that will probably have some traffic. > Right now I wrap every .php page in pg_connect() and pg_close(). > Then I read somewhere that Postgres only supports 100 simultaneous > connections (default). Is that a limitation? Should I use some other > method when writing code for high-traffic website?
I thought the out-of-the-box default was 32. If you honestly need a LOT of connections, you can configure the database to support more. I "upped the limit" on one system to have 512 the other week; certainly supportable, if you have the RAM for it. It is, however, quite likely that the connect()/close() cuts down on the efficiency of your application. If PHP supports some form of "connection pooling," you should consider using that, as it will cut down _dramatically_ on the amount of work done establishing/closing connections, and should let your apps use somewhat fewer connections more effectively. -- (format nil "[EMAIL PROTECTED]" "cbbrowne" "acm.org") http://cbbrowne.com/info/linux.html "It has been said that man is a rational animal. All my life I have been searching for evidence which could support this." -- Bertrand Russell ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
