Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fA6JF1m90051 for ; Tue, 6 Nov 2001 14:15:01 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fA6JEuc17265; Tue, 6 Nov 2001 14:14:56 -0500 (EST) To: "Ligia Pimentel" cc: pgsql-sql@postgresql.org Subject: Re: Left join error In-reply-to: <9s6j7s$2vvf$1@news.tht.net> References: <9s6j7s$2vvf$1@news.tht.net> Comments: In-reply-to "Ligia Pimentel" message dated "Mon, 05 Nov 2001 11:39:02 -0600" Date: Tue, 06 Nov 2001 14:14:56 -0500 Message-ID: <17262.1005074096@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/72 X-Sequence-Number: 5456 "Ligia Pimentel" writes: > I have a table with 146000+ records. I tried to select with a left join to > another table but I get this message: > ERROR: MemoryContextAlloc: invalid request size 4294967293 Hmm. This might indicate corrupted data --- do you see a similar error if you just do "select * from cheques" or "select * from formasenblanco"? If not, then I think you've run into a software bug. It'd be worth while to update to 7.1.3 before pursuing it further. If you still see the failure in 7.1.3 then I would like to see an EXPLAIN of the join query as well as a stack backtrace from the error. The easiest way to get the stack trace is in window 1: fire up psql in window 2: use ps to determine PID of the backend your psql is connected to gdb /path/to/postgres-executable -- do this as postgres user gdb> attach backend-PID-found-above gdb> break elog gdb> continue in window 1: issue the problem query in window 2: gdb should report reaching the breakpoint. Do gdb> bt --- copy & paste results printed here gdb> quit regards, tom lane