From: Johann Spies <jspies@sun.ac.za>
To: pgsql-admin@postgresql.org
Subject: Re: ERROR: invalid memory alloc request size
Date: Mon, 28 May 2007 15:45:59 +0200
Message-ID: <20070528134559.GC5615@sun.ac.za> (raw)
In-Reply-To: <10687.1179758440@sss.pgh.pa.us>
References: <20070514131318.GA26537@sun.ac.za>
<11217.1179153258@sss.pgh.pa.us>
<20070515105042.GA8121@burger.sun.ac.za>
<5221.1179337804@sss.pgh.pa.us>
<20070517132033.GA9482@sun.ac.za>
<25608.1179412804@sss.pgh.pa.us>
<20070518122942.GA28931@sun.ac.za>
<27574.1179501021@sss.pgh.pa.us>
<20070521140718.GC10742@sun.ac.za>
<10687.1179758440@sss.pgh.pa.us>
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
#4 0x00000000004c5393 in CopyReadLine (cstate=0x930d50) at copy.c:2210
#5 0x00000000004c7203 in DoCopy (stmt=0x90c590) at copy.c:1894
#6 0x000000000058110d in ProcessUtility (parsetree=0x90c590, params=0x0, dest=0x90c630, completionTag=0x7fffbf08d660 "")
at utility.c:635
#7 0x000000000057e76c in PortalRunUtility (portal=0x93a570, query=0x90c6c0, dest=0x90c630,
completionTag=0x7fffbf08d660 "") at pquery.c:1067
#8 0x000000000057f58d in PortalRunMulti (portal=0x93a570, dest=0x5, altdest=0x90c630, completionTag=0x7fffbf08d660 "")
at pquery.c:1135
#9 0x000000000057fd34 in PortalRun (portal=0x93a570, count=9223372036854775807, dest=0x90c630, altdest=0x90c630,
completionTag=0x7fffbf08d660 "") at pquery.c:700
#10 0x000000000057bde5 in exec_simple_query (
query_string=0x90c180 "COPY squidlogs FROM STDIN DELIMITER ' ' CSV QUOTE AS '\"'") at postgres.c:939
#11 0x000000000057d210 in PostgresMain (argc=4, argv=<value optimized out>, username=0x87c720 "js") at postgres.c:3424
#12 0x0000000000556b6a in ServerLoop () at postmaster.c:2931
#13 0x0000000000557707 in PostmasterMain (argc=3, argv=0x877370) at postmaster.c:963
#14 0x0000000000519403 in main (argc=3, argv=<value optimized out>) at main.c:188
Regards
Johann
--
Johann Spies Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch
"Wait on the LORD; be of good courage, and he shall
strengthen thine heart; wait, I say, on the LORD."
Psalms 27:14
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jspies@sun.ac.za
Subject: Re: ERROR: invalid memory alloc request size
In-Reply-To: <20070528134559.GC5615@sun.ac.za>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox