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

Re: ERROR: invalid memory alloc request size

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Johann Spies <jspies(at)sun(dot)ac(dot)za>, pgsql-admin(at)postgresql(dot)org
Subject: Re: ERROR: invalid memory alloc request size
Date: 2007-05-28 14:46:51
Message-ID: (view raw or whole thread)
Lists: pgsql-admin
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\" \"\" \"73\" \"\\\"\"\n\"2007-04-20\" \"18:07:06\" \"\" \"69\" \"\"\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              
"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)

In response to


pgsql-admin by date

Next:From: Tom LaneDate: 2007-05-28 15:18:37
Subject: Re: ERROR: invalid memory alloc request size
Previous:From: Johann SpiesDate: 2007-05-28 13:45:59
Subject: Re: ERROR: invalid memory alloc request size

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