pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gavin M. Roy <gmr@ehpg.net>
To: Frank Bax <fbax@sympatico.ca>
Cc: pgsql-php@postgresql.org
Subject: Re: too many clients
Date: Wed, 29 Dec 2004 15:32:11 -0800
Message-ID: <1104363131.32605.30.camel@localhost> (raw)
In-Reply-To: <5.2.1.1.0.20041229125718.00a02520@pop6.sympatico.ca>
References: <330532b604122908387f7ffde2@mail.gmail.com>
	<0DC9A380-59AB-11D9-B3B3-0003938BDF32@localnotion.com>
	<330532b604122908387f7ffde2@mail.gmail.com>
	<5.2.1.1.0.20041229125718.00a02520@pop6.sympatico.ca>

Per your direction, pg_pConnect is great when you have one site
dedicated on one box talking to another dedicated PgSQL box.  It does
not make sense in mass vhosting environments.  Using pg_pConnect greatly
reduces execution time in an environment where you're not fighting for
resources.  I use it on a few very high traffic sites without issue, but
it is tuned so that there is only 1 persistant connection per apache
backend and postgresql will allow the max apache backends, which by
default is generally 256.  I highly recommend it in such a situation,
while I generally do not recommend it in any other.

Gavin


On Wed, 2004-12-29 at 13:13 -0500, Frank Bax wrote:
> At 12:12 PM 12/29/04, Matthew Terenzio wrote:
> 
> 
> >On Dec 29, 2004, at 11:38 AM, Mitch Pirtle wrote:
> >
> >>You got a couple solutions, one of which is getting a connection
> >>pooler setup between apache(php) and postgres.  SQL Relay
> >>(sqlrelay.sf.net) could be a common candidate, as I have used it in
> >>the past with great results.
> >
> >Yes, I have taken a look at that before. It might be a good time to try it.
> >
> >I don't exactly understand the technical difference between pooled 
> >connections and persistent ones.
> >
> >pg_pconnect() is grabbing an existing open connection if one is available.
> >
> >How is  a connection pool more efficient in doing something along these lines?
> 
> 
> Have you read the php docs on persistent connections?
>          http://www.php.net/manual/en/features.persistent-connections.php
> pg_pconnect is sometimes used in situations where it does not make sense.
> 
> As you mentioned, apache uses numerous child process.  A persistent 
> connection can only be reused if the following things are the same:
>          - same apache child process requests the connection
>          - same connect string (ie host, database, user are *all* the same)
> 
> If you have a site where there are many databases and/or many users, it is 
> very easy for apache to retain more persistent connections than your 
> postgres limit.  There are many variables when trying to figure out which 
> function works better, so simply try it on your own system.  If pg_connect 
> does not add significant overhead, and manages to avoid the problems you 
> mentioned, then use it instead of pg_pconnect.
> 
> I haven't heard of pooled connections, but can only assume they somehow 
> overcome the problems with pg_pconnect gets out of control - perhaps the 
> connections are shared across apache child processes.
> 
> Frank 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org




view thread (15+ messages)  latest in thread

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

 · 

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: gmr@ehpg.net, fbax@sympatico.ca
  Subject: Re: too many clients
  In-Reply-To: <1104363131.32605.30.camel@localhost>
  References: <330532b604122908387f7ffde2@mail.gmail.com> <0DC9A380-59AB-11D9-B3B3-0003938BDF32@localnotion.com> <5.2.1.1.0.20041229125718.00a02520@pop6.sympatico.ca> <1104363131.32605.30.camel@localhost>

* 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