Postgres Pro
Downloads
Home   >   mailing lists

RE: pg_connect vs. pg_pconnect - Mailing list pgsql-php

From Hunter, Ray
Subject RE: pg_connect vs. pg_pconnect
Date
Msg-id 59358A738F45D51186A30008C74CE2500A084B@slc-exc1.ctron.com
Whole thread Raw
In response to pg_connect vs. pg_pconnect  ("Hunter, Ray" <rhunter@enterasys.com>)
Responses RE: pg_connect vs. pg_pconnect
List pgsql-php
Tree view
I took the advise of Brent Matzelle about 'not mixing connections' and switched to using pg_connect.  This has solved all my problems.  I am currently using php4.0.4pl1-9 and postgres 7.0.3 on Redhat 7.1.
 
I have no connections that are persisent and found that even with all my queries I can use the same connection.





RAY HUNTER
Automated Test Group
Software Support Engineer

ENTERASYS NETWORKS

rhunter@enterasys.com

www.enterasys.com

-----Original Message-----
From: Leonello, Chris (C.R.) [mailto:cleonell@visteon.com]
Sent: Friday, August 10, 2001 11:45 AM
To: 'Hunter, Ray'; 'Chris Ruprecht'
Cc: Pgsql-php (E-mail)
Subject: RE: pg_connect vs. pg_pconnect

Note that pg_close will not close persistent links (this is stated in the docs).  I have not found anything in the PHP docs that indicates what will close a persistent connection.
 
However, I do believe there is a bug.  I noticed with php version 4.03pl1 and PostgreSQL 7.03 that I would receive errors like "not a valid PostgreSQL result resource" when trying use persistent connections and had dozens of lingering postgres processes.  Apparently, not only was PHP not detecting existing open persistent connections and using them, it was then getting confused as it opened new connections.  I did not have this problem with an earlier version of PHP (possibly 4.01?) that I was using on a development server.  When I switched to pg_connect, the problem disappeared.
 
There are bug reports on php.net relating to this problem, (#8769, #12558, #11771, ...).  There have been other posts to the list (2/5/01 and 4/18/01) which I believe all point to this same problem with persistent connections not working and/or lingering forever.  I don't have any solutions, but I would be interested to hear from anyone having similar problems because I think this is wide spread (for those using p_connect).  Maybe we will stumble across some solution or I will gather enough info to put together one coherent and specific bug report.  Current bug reports are either closed because the were too vague, closed with the response that persistent connections are not supposed to close (never ever close...?) or still unassigned.
-----Original Message-----
From: Hunter, Ray [mailto:rhunter@enterasys.com]
Sent: Thursday, August 09, 2001 9:02 AM
To: 'Chris Ruprecht'
Cc: Pgsql-php (E-mail)
Subject: RE: pg_connect vs. pg_pconnect

Chris,
 
I am currently doing testing right now and finding that this is the case.  I think that there is some kind of bug.  I have to go in and manually kill the sleeping processes that are remaining after the pg_pconnect calls. 
 
Another question for you is why does pg_pconnect work when pg_connect does not.  I am running into this problem as I change some of the connections to pg_connect from pg_pconnect?
 

Thanks,


RAY HUNTER
Automated Test Group
Software Support Engineer

ENTERASYS NETWORKS

rhunter@enterasys.com

www.enterasys.com


 

-----Original Message-----
From: Chris Ruprecht [mailto:chrup999@yahoo.com]
Sent: Thursday, August 09, 2001 6:52 AM
To: Hunter, Ray
Subject: Re: [PHP] pg_connect vs. pg_pconnect

Ray,
 
I had the same problem (PG 7.1.2 on RedHat 7.0) and changed the procedures to only use pg_connect. The is probably a bug in the pg_pconnect ... pg_close functions.
 
Best regards,
Chris
 
----- Original Message -----
Sent: Thursday, August 09, 2001 7:42 AM
Subject: RE: [PHP] pg_connect vs. pg_pconnect

I am using both.  When I use pg_pconnect it seems that the connections are still sleeping even after I close the connection ( pg_close( $conn ) ).


 
 
 
RAY HUNTER
Automated Test Group
Software Support Engineer
 
ENTERASYS NETWORKS
 
Internal:    53888
Phone:       801 887-9888
Fax:         801 972-5789
Cellular:    801 698-0622

rhunter@enterasys.com
 
www.enterasys.com

-----Original Message-----
From: Mitch Vincent [mailto:mvincent@cablespeed.com]
Sent: Wednesday, August 08, 2001 6:10 PM
To: Hunter, Ray; pgsql-php@postgresql.org
Subject: Re: [PHP] pg_connect vs. pg_pconnect

If you're using pg_connect they should be terminating... Are you using
pg_connect or pg_pconnect?

-Mitch
Software development :
You can have it cheap, fast or working. Choose two.

----- Original Message -----
From: "Hunter, Ray" <rhunter@enterasys.com>
To: <pgsql-php@postgresql.org>
Sent: Wednesday, August 08, 2001 7:40 PM
Subject: [PHP] pg_connect vs. pg_pconnect

> I understand the difference between the two functions.  However, when I
> watch my process under process management I notice that I have tons of
> sleeping process that are lingering.  How can I make it so that when I
> connect to postgres and query that the connect process is then terminated?
> These sleeping connections are eating up my resources.
>
>
> Any suggestions?
>
>
>
> RAY HUNTER
> Automated Test Group
> Software Support Engineer
>
> ENTERASYS NETWORKS
>
> Internal:    53888
> Phone:       801 887-9888
> Fax:         801 972-5789
> Cellular:    801 698-0622
>
> rhunter@enterasys.com
>
> www.enterasys.com
>

pgsql-php by date:

Previous
From: "Brent R. Matzelle"
Date:
Subject: RE: pg_connect vs. pg_pconnect
Next
From: "Leonello, Chris (C.R.)"
Date:
Subject: RE: pg_connect vs. pg_pconnect