Aside from Apache children, pconnect doesn't really have any advantage
over connect... straight from the php.net doc...
You can use $GLOBALS to pass connections instead of trying to use the
pconnect string over and over.
If you write a quick function _one_ function that checks to see if a
connection is made, and uses that resource - or makes a new one, then all
you should have to do is include() that function in each one of your
pages....
Do you need an example? Send us one of yours, and we'll show you (at
least I will). I'd like to see what exactly you're using the pconnect
for.
Regards,
On Mon, 28 Jan 2002, 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
>
Chadwick Rolfs - cmr@gis.net
Cleveland State University - Student
Music Major - The Holden Arboretum Volunteer
Computer Programmer - Student Employee
--*I finally found powdered water;
I just can't figure out what to add to it*--
