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 1D5A78B9BC4 for ; Tue, 1 Feb 2005 17:10:31 +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 93567-04 for ; Tue, 1 Feb 2005 17:10:29 +0000 (GMT) Received: from trickle.cc.mcgill.ca (trickle.CC.McGill.CA [132.206.27.51]) by svr1.postgresql.org (Postfix) with ESMTP id 331108B9BBB for ; Tue, 1 Feb 2005 17:10:27 +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 j11HADiL000022; Tue, 1 Feb 2005 12:10:18 -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 j11HABQ2020626; Tue, 1 Feb 2005 12:10:11 -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: <200502011740.48639.vygen@planwerk6.de> References: <200502010938.17853.vygen@gmx.de> <1107263917.11348.10.camel@mafalda.corporateunderground.org> <200502011740.48639.vygen@planwerk6.de> Content-Type: text/plain Date: Tue, 01 Feb 2005 12:10:32 -0500 Message-Id: <1107277832.12116.1.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/4 X-Sequence-Number: 2978 On Tue, 2005-02-01 at 17:40 +0100, Janning Vygen wrote: > Am Dienstag, 1. Februar 2005 14:18 schrieben Sie: > > On Tue, 2005-02-01 at 09:38 +0100, Janning Vygen wrote: > > > Does anybody has any hints to solve this problem? > > > > This is a bit of a non-solution, but it is what worked for us. We > > simply stopped using pconnect() altogether. This seemed to have solved > > connection timeouts and delays. Our site gets 500k page hits per day > > without any problems. > > hm. i didn't get the point. Do you mean you don't use persistent connections > just plain pg_connect instead of pg_pconnect?? Exactly. pg_pconnect() is (or was the last time I tried it) broken in PHP. We were constantly getting connections that wouldn't close, and sometimes not time out. Ever since we gave up on them, we've had no problems. Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017