Skip site navigation (1) Skip section navigation (2)

RE: pg_connect vs. pg_pconnect

From: "Leonello, Chris (C(dot)R(dot))" <cleonell(at)visteon(dot)com>
To: "'Hunter, Ray'" <rhunter(at)enterasys(dot)com>, "'Chris Ruprecht'" <chrup999(at)yahoo(dot)com>
Cc: "Pgsql-php (E-mail)" <pgsql-php(at)postgresql(dot)org>
Subject: RE: pg_connect vs. pg_pconnect
Date: 2001-08-10 17:45:23
Message-ID: 200108101745.f7AHjOp11697@dymwsm12.mailwatch.com (view raw or flat)
Thread:
Lists: pgsql-php
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(at)enterasys(dot)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(at)enterasys(dot)com

www.enterasys.com <http://www.enterasys.com> 


 

-----Original Message-----
From: Chris Ruprecht [mailto:chrup999(at)yahoo(dot)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 ----- 
From: Hunter,  <mailto:rhunter(at)enterasys(dot)com> Ray 
To: Pgsql-php (E-mail) <mailto:pgsql-php(at)postgresql(dot)org>  
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(at)enterasys(dot)com 
  
www.enterasys.com 


-----Original Message----- 
From: Mitch Vincent [ mailto:mvincent(at)cablespeed(dot)com
<mailto:mvincent(at)cablespeed(dot)com> ] 
Sent: Wednesday, August 08, 2001 6:10 PM 
To: Hunter, Ray; pgsql-php(at)postgresql(dot)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(at)enterasys(dot)com> 
To: <pgsql-php(at)postgresql(dot)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(at)enterasys(dot)com 
> 
> www.enterasys.com 
> 

pgsql-php by date

Next:From: Hunter, RayDate: 2001-08-10 17:57:08
Subject: RE: pg_connect vs. pg_pconnect
Previous:From: Brent R. MatzelleDate: 2001-08-09 13:49:19
Subject: RE: pg_connect vs. pg_pconnect

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group