php-bugs

ID: 31411
Comment by: ctrix at hotmail dot com
Reported By: mike at ecommerce dot com
Status: No Feedback
Bug Type: PostgreSQL related
Operating System: *
PHP Version: 5CVS, 4CVS (2005-01-17)
New Comment:

Same problem here with PHP 5.2.0.
It's easily reproduceable: simply start a persistent connection, then
restart postgres.

That message will appear.


Previous Comments:
------------------------------------------------------------------------

[2005-07-14 01:00:03] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

------------------------------------------------------------------------

[2005-07-06 13:06:59] sniper@php.net

Please try using this CVS snapshot:

http://snaps.php.net/php5-latest.tar.gz

For Windows:

http://snaps.php.net/win32/php5-win32-latest.zip

------------------------------------------------------------------------

[2005-04-11 09:28:11] exaton at free dot fr

I believe I might be experiencing something similar. Setup is PHP 5.0.4
on Apache 2.0.53 under WinXP SP2.

I've just upgraded to PG 8.0.2. With PG 8.0.1, I had to use persistent
connections to my (also local) database, otherwise the connection time
was absolutely prohibitive. The PG team have apparently solved this
issue, so I've dropped persistence as it was cluttering up my system
unnecessarily.

So now with PG 8.0.2, I'm getting "PHP Notice: Unknown: Cannot set
connection to blocking mode in Unknown on line 0" at the end of PHP
output, _sporadically_. Not systematically, rather when the page hasn't
been reloaded in a little while (3-4 minutes can suffice).

It's not messing up the page apart from the notice output ; the rest of
the SQL in my scripts works just fine.

------------------------------------------------------------------------

[2005-01-18 12:20:07] mike at ecommerce dot com

No, i am afraid, setting pgsql.auto_reset_persistent = On doesn't
change anything.

Looking at the code in ext/pgsql/pgsql.c, this setting is only used in
pg_connect, but has no influence in the function in question,
_rollback_transactions.

------------------------------------------------------------------------

[2005-01-18 09:35:46] yohgaki at ohgaki dot net

I've forgot I've implemented auto persistent connection reset feature.

Try to change following ini setting to On.
----
; Detect broken persistent links always with pg_pconnect().
; Auto reset feature requires a little overheads.
pgsql.auto_reset_persistent = Off
----

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/31411

--
Edit this bug report at http://bugs.php.net/?id=31411&edit=1