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

Re: Bug in backend/lib/stringinfo.c:enlargeStringInfo()

From: Nick Wellnhofer <wellnhofer(at)aevum(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug in backend/lib/stringinfo.c:enlargeStringInfo()
Date: 2004-05-11 20:35:14
Message-ID: 40A13902.3080406@aevum.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Nick Wellnhofer <wellnhofer(at)aevum(dot)de> writes:
>>The real cause of the problem seems to be a frontend/backend 
>>communication problem. The "needed" argument 0x5454502b comes from a 
>>4-byte length field which string content is 'TTP/'. Looks like a part of 
>>a HTTP request to me.
> 
> 
> Yeah, it kinda sounds like someone is trying to send an HTTP request to
> the Postgres port :-(

I thought about that, but I have TCP disabled. And it's definitely 
triggered by my own Perl code serving dynamic web pages. But it happens 
at completely random places. Maybe it's a bug in DBD::Pg. Is there an 
easy way to log the whole frontend/backend communication?

Nick


-- 
aevum gmbh
leopoldstr. 87
80802 m√ľnchen
germany

fon: +4989 38380653
fax: +4989 38799384
wellnhofer(at)aevum(dot)de
http://aevum.de/

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-05-11 20:54:04
Subject: Re: Bug in backend/lib/stringinfo.c:enlargeStringInfo()
Previous:From: Tom LaneDate: 2004-05-11 20:10:19
Subject: Re: Bug in backend/lib/stringinfo.c:enlargeStringInfo()

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