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 E85C68B9E78 for ; Tue, 1 Feb 2005 13:18:01 +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 72542-04 for ; Tue, 1 Feb 2005 13:17:49 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by svr1.postgresql.org (Postfix) with ESMTP id 9DAE98B9E67 for ; Tue, 1 Feb 2005 13:17:51 +0000 (GMT) Received: from 192.168.123.100 ([66.130.41.190]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IB800M7NI9R3V@VL-MO-MR007.ip.videotron.ca> for pgsql-php@postgresql.org; Tue, 01 Feb 2005 08:17:51 -0500 (EST) Date: Tue, 01 Feb 2005 08:18:36 -0500 From: Christopher Murtagh Subject: Re: How to handle missing pgsql.connect_timeout In-reply-to: <200502010938.17853.vygen@gmx.de> To: Janning Vygen Cc: pgsql-php@postgresql.org Message-id: <1107263917.11348.10.camel@mafalda.corporateunderground.org> MIME-version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT References: <200502010938.17853.vygen@gmx.de> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200502/2 X-Sequence-Number: 2976 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. Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017