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

New PostgrSQL Errors

From: David Wheeler <david(at)kineticode(dot)com>
To: SF Postgres <sfpug(at)postgresql(dot)org>
Subject: New PostgrSQL Errors
Date: 2004-03-18 23:28:39
Message-ID: FCC71C7A-7933-11D8-B724-000A95972D84@kineticode.com (view raw or flat)
Thread:
Lists: sfpug
Hi All,

Suddenly, I'm getting a lot of this sort of thing in my Apache log for 
Bricolage:

message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
DBD::Pg::st execute warning:  [for Statement "
         SELECT p.id, p.name, p.description, p.def, p.value, p.manual, 
p.opt_type, o.description, p.can_be_overridden, m.grp__id
         FROM   pref p, pref_opt o, member m, pref_member c
         WHERE  p.id = o.pref__id AND p.value = o.value AND p.id = 
c.object_id AND m.id = c.member__id AND m.active = 1 AND LOWER(p.name) 
LIKE ?
         ORDER BY p.name, p.id
     "] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 996.
[Thu Mar 18 22:46:18 2004] [error] Unable to fetch row from statement 
handle: DBD::Pg::st fetch failed: no statement executing [for Statement 
"
         SELECT p.id, p.name, p.description, p.def, p.value, p.manual, 
p.opt_type, o.description, p.can_be_overridden, m.grp__id
         FROM   pref p, pref_opt o, member m, pref_member c
         WHERE  p.id = o.pref__id AND p.value = o.value AND p.id = 
c.object_id AND m.id = c.member__id AND m.active = 1 AND LOWER(p.name) 
LIKE ?
         ORDER BY p.name, p.id
     "] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1128.

[/usr/local/bricolage/lib/Bric/Util/DBI.pm:1129]
[/usr/local/bricolage/lib/Bric/Util/Pref.pm:1314]
[/usr/local/bricolage/lib/Bric/Util/Pref.pm:205]
[/usr/local/bricolage/lib/Bric/App/Util.pm:397]
[/usr/local/bricolage/lib/Bric/App/Handler.pm:293]


Any idea what those messages are and why they'd be hosing my statement 
handles? FWIW, the statement handle _should_ be executing; execute() is 
called five lines before the error is generated in Pref.pm line 1314.

TIA,

David


Responses

sfpug by date

Next:From: David WheelerDate: 2004-03-18 23:39:34
Subject: Re: New PostgrSQL Errors
Previous:From: David FetterDate: 2004-03-18 21:53:56
Subject: Re: Last Meeting and Our Name

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