When grilled further on (Sat, 24 Jan 2004 15:54:07 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> > A custom Perl 5.6.1, DBI 1.30, DBD::Pg 1.22 script on Solaris 5.8.
> > Using pgsql client version 7.3.3. I'm thinking it may be related to
> > my forking? My program has a db connection, which
When grilled further on (Thu, 22 Jan 2004 22:19:44 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > What more information would you be looking for?
>
> Well, in the words of the old saw, if we knew what we were looking for
> it wouldn't be research
Robert Creager <[EMAIL PROTECTED]> writes:
> What more information would you be looking for?
Well, in the words of the old saw, if we knew what we were looking for
it wouldn't be research ...
I'm sure we could solve it quickly if we could get a reproducible test
case, but it sounds like you are n
When grilled further on (Thu, 22 Jan 2004 14:27:19 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Description:message type 0x49 arrived from server while idle
>
> Hm. This would seem to have something to do with issuing empty quer
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:message type 0x49 arrived from server while idle
Hm. This would seem to have something to do with issuing empty queries
(message type 0x49 = 'I' is EmptyQueryResponse). I couldn't duplicate the
problem in some simple tests,
The following bug has been logged online:
Bug reference: 1061
Logged by: Robert Creager
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux Mandrake 9.2 2.4.22 SMP
Description:message type 0x49 arrived from server while idle
Details:
