Re: New PostgrSQL Errors

From: David Wheeler <david(at)kineticode(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: SF Postgres <sfpug(at)postgresql(dot)org>
Subject: Re: New PostgrSQL Errors
Date: 2004-03-19 00:25:11
Message-ID: E2121462-793B-11D8-B724-000A95972D84@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: sfpug

I managed to get a stack trace on the warning issued by DBD::Pg:

message type 0x49 arrived from server while idle

[/usr/local/lib/perl5/site_perl/5.8.3/darwin-2level/DBD/Pg.pm:180]
[/usr/local/lib/perl5/site_perl/5.8.3/darwin-2level/DBI.pm:1302]
[/usr/local/lib/perl5/site_perl/5.8.3/darwin-2level/DBI.pm:587]
[/usr/local/lib/perl5/site_perl/5.8.3/darwin-2level/DBI.pm:646]
[/usr/local/lib/perl5/site_perl/5.8.3/darwin-2level/DBI.pm:498]
[/usr/local/bricolage/lib/Bric/Util/DBI.pm:1661]
[/usr/local/bricolage/lib/Bric/Util/DBI.pm:557]
[/usr/local/bricolage/lib/Bric/App/CleanupHandler.pm:125]

Line 180 of Pg.pm is

my $ret = DBD::Pg::db::_pg_type_info($pg_type);

_pg_type_info is a Perl XS/C function:

_pg_type_info (type_sv=Nullsv)
SV* type_sv
CODE:
{
# int type_num = VARCHAROID;
int type_num = 0;
sql_type_info_t *type_info;

if(type_sv && SvOK(type_sv)) {
if SvMAGICAL(type_sv)
mg_get(type_sv);

type_info = pg_type_data(SvIV(type_sv));
type_num = type_info ? type_info->type.sql :
SQL_VARCHAR;
}
RETVAL = type_num;
XST_mIV(0, RETVAL);
}

Ugly, isn't it? I'll post to the DBD::Pg list to see if anyone there
has any idea. In the meantime, does anyone know what "message type
0x49" or "0x5a" are?

Thanks for the help.

Regards,

David

In response to

Responses

Browse sfpug by date

  From Date Subject
Next Message Dror Matalon 2004-03-19 00:31:37 Re: New PostgrSQL Errors
Previous Message Josh Berkus 2004-03-19 00:22:54 Re: New PostgrSQL Errors