Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5BA149FBF39 for ; Thu, 17 May 2007 11:40:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 77583-04 for ; Thu, 17 May 2007 11:39:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id BE5379FC008 for ; Thu, 17 May 2007 11:40:05 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4HEe48I025609; Thu, 17 May 2007 10:40:04 -0400 (EDT) To: Johann Spies cc: pgsql-admin@postgresql.org Subject: Re: ERROR: invalid memory alloc request size In-reply-to: <20070517132033.GA9482@sun.ac.za> 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> Comments: In-reply-to Johann Spies message dated "Thu, 17 May 2007 15:20:33 +0200" Date: Thu, 17 May 2007 10:40:04 -0400 Message-ID: <25608.1179412804@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/166 X-Sequence-Number: 25486 Johann Spies writes: > Breakpoint 1, 0x0827eef6 in errfinish () > (gdb) bt > #0 0x0827eef6 in errfinish () > #1 0x0828039c in elog_finish () > #2 0x082993b3 in MemoryContextAlloc () > #3 0x0828d437 in pg_mb2wchar () > #4 0x0811c288 in CreateCopyDestReceiver () > #5 0x0811ea43 in DoCopy () > #6 0x081f9d00 in ProcessUtility () > #7 0x081f6ed9 in PostgresMain () > #8 0x081f7cac in FreeQueryDesc () > #9 0x081f84d9 in PortalRun () > #10 0x081f3b51 in pg_parse_query () > #11 0x081f5296 in PostgresMain () > #12 0x081c8a1f in ClosePostmasterPorts () > #13 0x081c9924 in PostmasterMain () > #14 0x081823b5 in main () Hmmm ... this is interesting, but unfortunately backtraces from non-debug builds are often not very trustworthy, and that seems to have happened here. CreateCopyDestReceiver doesn't call pg_mb2wchar, and pg_mb2wchar doesn't call MemoryContextAlloc, so we're being lied to right at the spot where we might've hoped to learn something. Could you please rebuild the executables with --enable-debug and try again? regards, tom lane