#31411 [Com]: Misplaced "Cannot set connection to blocking mode" at end of output
ID: 31411 Comment by: wmoran at potentialtech 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: I can reproduce this on both PHP 5.2.6 and 5.2.8 using PostgreSQL 8.3.6 client/server on FreeBSD 6.3 Further, the error reporting is odd. No setting of error_reporting in my php.ini seems to squelch it. Previous Comments: [2008-11-06 17:59:33] benjiro at benjiro dot com This problem has also confirmed in PHP Version 5.2.6-2+b1. Recreate: Run your test script with a permanent connection. Restart postgresql for whatever reason. Enjoy this nice "NOTICE on 06-11 18:58 with response pg_query_params() [function.pg-query-params]: Cannot set connection to blocking mode". Also note: Don't forget to clear your browser cache afterward, or else your going to keep getting this message when you refresh a page ( F5 ). Making it worse then it is. [2008-08-21 07:41:16] igor dot kotsarev at gloru dot net Same problem on PHP 5.26 [2007-11-19 21:18:40] ctrix at hotmail dot com Same problem here with PHP 5.2.0. It's easily reproduceable: simply start a persistent connection, then restart postgres. That message will appear. [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] sni...@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 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
Bug #31411 [Com]: Misplaced "Cannot set connection to blocking mode" at end of output
Edit report at http://bugs.php.net/bug.php?id=31411&edit=1 ID: 31411 Comment by: wmoran at potentialtech dot com Reported by:mike at ecommerce dot com Summary:Misplaced "Cannot set connection to blocking mode" at end of output Status: No Feedback Type: Bug Package:PostgreSQL related Operating System: * PHP Version:5CVS, 4CVS (2005-01-17) Block user comment: N New Comment: I can no longer reproduce this problem on PHP 5.3.3 running on FreeBSD 8.1 against PostgreSQL 8.4.4. Previous Comments: [2009-11-13 18:03:11] manuel dot garciah at ife dot org dot mx Hi, We are using PHP 5.1.6 with PostgrSQL 8.1.11, and we obtained the next message: http://bugs.php.net/captcha-image.php?x=1258135348&; Notice: pg_exec() [function.pg-exec]: Cannot set connection to blocking mode in /home/httpd/shtml/sg/derfe/funciones.inc on line 730 Notice: Unknown: Cannot set connection to blocking mode in Unknown on line 0 We use pg_pconnect, What do you suggest to use? or exist some versión in PHP where this bug was solved? [2009-02-20 18:23:41] wmoran at potentialtech dot com I can reproduce this on both PHP 5.2.6 and 5.2.8 using PostgreSQL 8.3.6 client/server on FreeBSD 6.3 Further, the error reporting is odd. No setting of error_reporting in my php.ini seems to squelch it. [2008-11-06 17:59:33] benjiro at benjiro dot com This problem has also confirmed in PHP Version 5.2.6-2+b1. Recreate: Run your test script with a permanent connection. Restart postgresql for whatever reason. Enjoy this nice "NOTICE on 06-11 18:58 with response pg_query_params() [function.pg-query-params]: Cannot set connection to blocking mode". Also note: Don't forget to clear your browser cache afterward, or else your going to keep getting this message when you refresh a page ( F5 ). Making it worse then it is. [2008-08-21 07:41:16] igor dot kotsarev at gloru dot net Same problem on PHP 5.26 [2007-11-19 21:18:40] ctrix at hotmail dot com Same problem here with PHP 5.2.0. It's easily reproduceable: simply start a persistent connection, then restart postgres. That message will appear. 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/bug.php?id=31411 -- Edit this bug report at http://bugs.php.net/bug.php?id=31411&edit=1
Req #35800 [Com]: pg_query_params fails to escape NULL in bytea fields
Edit report at http://bugs.php.net/bug.php?id=35800&edit=1 ID: 35800 Comment by: wmoran at potentialtech dot com Reported by:vinny at xs4all dot nl Summary:pg_query_params fails to escape NULL in bytea fields Status: Open Type: Feature/Change Request Package:PostgreSQL related Operating System: winxp sp2 PHP Version:5.1.1 Block user comment: N Private report: N New Comment: I can confirm this problem on FreeBSD 8.1 with PHP 5.3.5 and PostgreSQL 8.4.6. Note that it is ONLY parametrized queries that exhibit the problem. Proper use of pg_escape_bytea() and pg_unescape_bytea() works as expected. Previous Comments: [2006-07-10 14:09:15] burleybutler at hotmail dot com I too found using a parameter doesn't work for uploading bytea binary data - either unescaped (zero bytes got saved) or using pg_escape_bytea (too many bytes got saved). Was hoping it would get around the memory/speed problems with pg_escape_bytea for large chunks of data. [2005-12-25 12:53:00] vinny at xs4all dot nl Description: pg_query_params() stops processing binary 'bytea' field data at hex '00'. Reproduce code: --- Expected result: The image should be stored in the database completely. Actual result: -- Only the first four bytes of the JPG data make it into the database. JPG data starts with: hex FF D8 FF E0 00 10 4A 46 49 Apparently pg_query_params stops processing the content at '00' which I guess is because PHP thinks it is at 'EOF'. If you insert the data with a normal pg_query call and using pg_escape_bytea() on the JPG data then everything works just fine and the image is stored properly. -- Edit this bug report at http://bugs.php.net/bug.php?id=35800&edit=1
