Bug #65384 [Asn->Csd]: pg_last_notice test failures
Edit report at https://bugs.php.net/bug.php?id=65384&edit=1
ID: 65384
Updated by: yohgaki@php.net
Reported by: nikic@php.net
Summary: pg_last_notice test failures
-Status: Assigned
+Status: Closed
Type: Bug
Package: PostgreSQL related
PHP Version: 5.5.2RC1
Assigned To: yohgaki
Block user comment: N
Private report: N
New Comment:
It was error logging setting.
Setting error logging message solved issue.
I've only committed the fix. Should I commit the fix to 5.4/5.5?
Previous Comments:
------------------------------------------------------------------------
[2013-08-18 07:43:23] yohgaki@php.net
> Could it just be that they configured client_min_messages=WARNING?
Users can set it as SQL command.
SET client_min_messages TO WARNING;
It may be the reason why this test fails. I'll try to change message level to
NOTICE to see if it helps. I'm not sure how NOTIFY command is handled by
PostgreSQL, so it might not be related, though.
There is request that stores all notice during session. I'll work on this
request later. If pgsql module keep all of them, it may consume all available
memory. Therefore, configuration for max number of notices recorded will be
added. It may help to find out what is going on.
------------------------------------------------------------------------
[2013-08-09 20:35:53] mike@php.net
Could it just be that they configured client_min_messages=WARNING?
------------------------------------------------------------------------
[2013-08-05 01:18:45] yohgaki@php.net
I cannot reproduce on my Fedora19 and PHP 5.5 branch
[yohgaki@dev PHP-5.5]$ rpm -q postgresql
postgresql-9.2.4-1.fc19.x86_64
Anyone know what the PostgreSQL version on Travis CI?
------------------------------------------------------------------------
[2013-08-03 15:04:51] nikic@php.net
Description:
------------
The following pg_last_notice related tests currently fail on Travis CI:
PostgreSQL notice function [ext/pgsql/tests/09notice.phpt]
Bug #32223 (weird behaviour of pg_last_notice) [ext/pgsql/tests/80_bug32223.phpt]
Bug #32223 (weird behaviour of pg_last_notice using define) [ext/pgsql/tests/80_bug32223b.phpt]
The diffs are:
09notice.phpt:
001+ Cannot find notice message in hash
002+ bool(false)
003+
001- Notice: pg_query(): %s already a transaction in progress in %s on line %d
002- %s already a transaction in progress
80_bug32223.phpt:
005+ bool(false)
005- string(14) "NOTICE: 11111"
80_bug32223b.phpt:
005+ bool(false)
005- string(14) "NOTICE: 11111"
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=65384&edit=1
Thread (8 messages)