From: Mitch Vincent <mitch@doot.org>
To: Chris Ruprecht <chrup999@yahoo.com>
To: Frank Bax <fbax@sympatico.ca>
Cc: PostGreSQL PHP Group <pgsql-php@postgresql.org>
Subject: Re: pg_pconnect - ??
Date: Mon, 28 Jan 2002 12:56:59 -0700
Message-ID: <009a01c1a835$f2d76520$0200000a@Mitch> (raw)
References: <3.0.6.32.20020128141957.02130660@pop6.sympatico.ca>
Very true -- persistent connections are only going to give you a performance
gain of the time it takes to start a new PG process. That gain can matter
and matter a lot in certain situations but generally only with high-traffic
servers. Be careful, it's easy to run out of resources especially if you
have your PG processes set to use a good amount of sort/shared memory (and
you really should increase it from the default settings to get much better
performance)
Good luck!
-Mitch
----- Original Message -----
From: "Frank Bax" <fbax@sympatico.ca>
To: "Chris Ruprecht" <chrup999@yahoo.com>
Cc: "PostGreSQL PHP Group" <pgsql-php@postgresql.org>
Sent: Monday, January 28, 2002 12:19 PM
Subject: Re: [PHP] pg_pconnect - ??
> The connection will only be reused if the *same* apache child process
> handles the request. You should expect to see many postgres client
> connections.
> A) Each database/user connection combination.
> B) Each apache child process
>
> Multiply A*B to get max number of concurrent connections. If A*B can go
> over postgres connection limit, then you might start getting connection
> refused messages.
>
> If your postgres database is on the same server as you webserver, there is
> neglible gains for using pconnect over connect.
>
> Frank
>
>
> At 09:56 AM 1/28/02 -0600, Chris Ruprecht wrote:
> >Hi all,
> >
> >I am under the assumtion that, when I do a pg_pconnect instead of a
> >pg_connect, the connection to the db I have established, can be used
> >by another PHP procedure. Somehow, I don't see this working the way I
> >expect it.
> >When I initially connect with pconnect, I see a postgres session
> >staring up and everything works. The postgres process stays active
> >but when I pconnect again, a second process is started. I was
> >expecting that the same process from the first pconnect will be used.
> >At the end, I land up with a whole bunch of postgres client sessions
> >hanging around in the system, doing who knows what.
> >
> >What am I missing (doing wrong) here?
> >Postgres = 7.1.3, OS = Linux 2.4.9 (RedHat 7.2), PHP = 4.0.6, Apache
> >= 1.3.22, memory = plenty (768 MB)
> >
> >Best regards,
> >Chris
> >--
> >Chris Ruprecht
> >Network grunt and bit pusher extraordinaíre
> >
> >_________________________________________________________
> >Do You Yahoo!?
> >Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
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: mitch@doot.org, chrup999@yahoo.com, fbax@sympatico.ca
Subject: Re: pg_pconnect - ??
In-Reply-To: <009a01c1a835$f2d76520$0200000a@Mitch>
References: <3.0.6.32.20020128141957.02130660@pop6.sympatico.ca> <009a01c1a835$f2d76520$0200000a@Mitch>
* 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