pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Murtagh <christopher.murtagh@mcgill.ca>
To: Janning Vygen <vygen@planwerk6.de>
Cc: pgsql-php@postgresql.org
Subject: Re: How to handle missing pgsql.connect_timeout
Date: Wed, 02 Feb 2005 12:01:03 -0500
Message-ID: <1107363663.15805.20.camel@localhost.localdomain> (raw)
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>

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




view thread (8+ messages)  latest in thread

Message-ID: <1107363663.15805.20.camel@localhost.localdomain>
Permalink:  ../1107363663.15805.20.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1107363663.15805.20.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: christopher.murtagh@mcgill.ca, vygen@planwerk6.de
  Subject: Re: How to handle missing pgsql.connect_timeout
  In-Reply-To: <1107363663.15805.20.camel@localhost.localdomain>
  References: <200502010938.17853.vygen@gmx.de> <200502011740.48639.vygen@planwerk6.de> <1107277832.12116.1.camel@localhost.localdomain> <200502020949.21251.vygen@planwerk6.de> <1107363663.15805.20.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox