Thread: Postgress jobs stick around after they have completed
Hi all, This is on: RedHat Linux 7.0 Apache 1.3.20 PHP 4.0.6 PostGreSQL 7.1.2 I run a procedure which does a $conn = pg_connect(...); and later a $res = pg_close( $conn ); The later returns '1' as a result - not sure if that is good or bad (0 = false, 1 = true?). However, I have the completed job still hanging around when I do a ps -ef: postgres 7493 928 14 13:55 ? 00:00:34 postgres: apache phones [local] Where am I going wrong? Best regards, Chris _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
you have persistent connections enabled in php.ini?
You might want to have the connection be a "pg_pconnect()" and then use a close() to close the connection.
Ray
-----Original Message-----
From: Chris Ruprecht [mailto:chrup999@yahoo.com]
Sent: Monday, June 25, 2001 1:06 PM
To: p-php
Subject: [PHP] Postgress jobs stick around after they have completed
Hi all,
This is on:
RedHat Linux 7.0
Apache 1.3.20
PHP 4.0.6
PostGreSQL 7.1.2
I run a procedure which does a $conn = pg_connect(...); and later a $res =
pg_close( $conn );
The later returns '1' as a result - not sure if that is good or bad (0 =
false, 1 = true?). However, I have the completed job still hanging around
when I do a ps -ef:
postgres 7493 928 14 13:55 ? 00:00:34 postgres: apache phones
[local]
Where am I going wrong?
Best regards,
Chris
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
on 06/25/2001 23:09, Jason k Larson at jlarson@techpilots.net wrote: > Hello - > > Your result of 1 means the close was (supposedly) successful. Not > sure why you have processes still running though. I would certainly > expect this pg_pconnect .. are you certain that nowhere else in the > script is attempting persistent connections? Or was using persistent > connections .. when in doubt .. try restarting Apache (apachectl > restart) and see if this process goes away (as it should if PHP > launched it, etc.) Ok - I found the bug - I did a pg_pconnect(...). After I changed that to a pg_connect, the session terminated upon pg_close( ... ). Since I have not quite been able to locate any docs on PHP-PG connections and their commands - why would I use a persistent connection? What can I do with it? Will it stay open until - when? Thanks for your help guys!! Chris _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
You might want to have the connection be a "pg_pconnect()" and then use a close() to close the connection.
Ray
-----Original Message-----
From: Chris Ruprecht [mailto:chrup999@yahoo.com]
Sent: Monday, June 25, 2001 1:06 PM
To: p-php
Subject: [PHP] Postgress jobs stick around after they have completed
Hi all,
This is on:
RedHat Linux 7.0
Apache 1.3.20
PHP 4.0.6
PostGreSQL 7.1.2
I run a procedure which does a $conn = pg_connect(...); and later a $res =
pg_close( $conn );
The later returns '1' as a result - not sure if that is good or bad (0 =
false, 1 = true?). However, I have the completed job still hanging around
when I do a ps -ef:
postgres 7493 928 14 13:55 ? 00:00:34 postgres: apache phones
[local]
Where am I going wrong?
Best regards,
Chris
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?