Tom Lane wrote:
Nick Wellnhofer <[EMAIL PROTECTED]> 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 k
Nick Wellnhofer <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 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
Nick Wellnhofer <[EMAIL PROTECTED]> writes:
> I found out that the process was looping in enlargeStringInfo() in
> backend/lib/stringinfo.c.
This problem was reported by someone else recently. I've just applied
the attached patch.
> The real cause of the problem seems to be a frontend/backend
Hi,
for some time a postgres process on one of our web servers repeatedly
gets into an infinite loop. This happens very rarely, about once in a
week. Today I installed gdb on the server to trace down the problem.
I found out that the process was looping in enlargeStringInfo() in
backend/lib/st
