Skip site navigation (1) Skip section navigation (2)

Re: How to handle missing pgsql.connect_timeout

From: Christopher Murtagh <christopher(dot)murtagh(at)mcgill(dot)ca>
To: Janning Vygen <vygen(at)planwerk6(dot)de>
Cc: pgsql-php(at)postgresql(dot)org
Subject: Re: How to handle missing pgsql.connect_timeout
Date: 2005-02-01 17:10:32
Message-ID: 1107277832.12116.1.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-php
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



Christopher Murtagh
Enterprise Systems Administrator
ISR / Web Communications Group 
McGill University
Montreal, Quebec

Tel.: (514) 398-3122
Fax:  (514) 398-2017

In response to


pgsql-php by date

Next:From: Janning VygenDate: 2005-02-02 08:49:20
Subject: Re: How to handle missing pgsql.connect_timeout
Previous:From: Janning VygenDate: 2005-02-01 16:40:48
Subject: Re: How to handle missing pgsql.connect_timeout

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group