X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 201D78B9CC3 for ; Wed, 2 Feb 2005 17:01:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 21094-07 for ; Wed, 2 Feb 2005 17:01:27 +0000 (GMT) Received: from trickle.cc.mcgill.ca (trickle.CC.McGill.CA [132.206.27.51]) by svr1.postgresql.org (Postfix) with ESMTP id C3A408B9C8C for ; Wed, 2 Feb 2005 17:01:21 +0000 (GMT) Received: from mailscan2.cc.mcgill.ca (mailscan2.CC.McGill.CA [132.216.77.249]) by trickle.cc.mcgill.ca (8.12.11/8.12.3) with ESMTP id j12H0u58007354; Wed, 2 Feb 2005 12:01:02 -0500 (EST) Received: from brahma (brahma.WCG.McGill.CA [132.216.78.5]) by mailscan2.cc.mcgill.ca (8.13.0/8.13.0) with ESMTP id j12H0glI021700; Wed, 2 Feb 2005 12:00:44 -0500 (EST) Subject: Re: How to handle missing pgsql.connect_timeout From: Christopher Murtagh To: Janning Vygen Cc: pgsql-php@postgresql.org In-Reply-To: <200502020949.21251.vygen@planwerk6.de> References: <200502010938.17853.vygen@gmx.de> <200502011740.48639.vygen@planwerk6.de> <1107277832.12116.1.camel@localhost.localdomain> <200502020949.21251.vygen@planwerk6.de> Content-Type: text/plain Date: Wed, 02 Feb 2005 12:01:03 -0500 Message-Id: <1107363663.15805.20.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/5 X-Sequence-Number: 2979 On Wed, 2005-02-02 at 09:49 +0100, Janning Vygen wrote: > It's not broken anymore! And it speeds up your website. Well it might not be broken anymore, but I haven't seen any evidence of a speed increase (quite the opposite in fact). What we did instead was write a very small abstraction layer so that any page request would only use 1 database connection. We're running on dual 2.8 GHz Xeons for our web server and db machine and taking on over 500,000 hits per day. Some of our pages are very data intensive (http://www.mcgill.ca/calendar/ for example). > At the moment it waits "forever" (until max_execution_time i guess) and you > have no chance to show an error message like: DB is overloaded, please try > again. maybe pg_pconnect() isn't all it is cracked up to be? Anyone else here have good experiences with it? Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017