Re: ERROR: invalid memory alloc request size

Johann Spies wrote:
> On Mon, May 21, 2007 at 10:40:40AM -0400, Tom Lane wrote:
> > Well, if you aren't having any luck debugging it yourself, maybe you
> > could put together a self-contained test case for someone else to
> > reproduce the problem with?
>
> Hallo Tom,
>
> Sorry for the long delay.
>
> Maybe the following was what you were looking for:
>
>
> gdb) bt
> #0 errfinish (dummy=0) at elog.c:313
> #1 0x00000000005f40c1 in elog_finish (elevel=<value optimized out>, fmt=<value optimized out>) at elog.c:939
> #2 0x0000000000609585 in MemoryContextAlloc (context=0x941210, size=1350958157) at mcxt.c:504
> #3 0x00000000005ff1c8 in perform_default_encoding_conversion (
> src=0x2b881e87f040 "\"2007-04-20\" \"18:07:06\" \"192.168.0.100\" \"73\" \"http://www.kerkbode.co.za/kerkbode/images/blank.gif\\\"\"\n\"2007-04-20\" \"18:07:06\" \"192.168.0.100\" \"69\" \"http://develop.christians.co.za/phpAdsNew/adx.js\"\n\"20"..., len=337739539, is_client_to_server=5 '\005') at mbutils.c:461

Interesting. You are passing a single 300 MB string here, not
90-something char lines. The problem is probably in newlines. Why are
they not getting used as line separators escapes me.

--
Alvaro Herrera http://www.advogato.org/person/alvherre
"There is evil in the world. There are dark, awful things. Occasionally, we get
a glimpse of them. But there are dark corners; horrors almost impossible to
imagine... even in our worst nightmares." (Van Helsing, Dracula A.D. 1972)