Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBMGW0612375 for ; Fri, 22 Dec 2000 11:32:00 -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.1/8.11.1) with ESMTP id eBMGVXC12183; Fri, 22 Dec 2000 11:31:33 -0500 (EST) To: Najm Hashmi cc: "pgsql-sql@postgresql.org" Subject: Re: pg_dump Error In-reply-to: <3A43A33D.4151FAFD@mondo-live.com> References: <3A43A33D.4151FAFD@mondo-live.com> Comments: In-reply-to Najm Hashmi message dated "Fri, 22 Dec 2000 13:53:49 -0500" Date: Fri, 22 Dec 2000 11:31:33 -0500 Message-ID: <12180.977502693@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/262 X-Sequence-Number: 599 Najm Hashmi writes: > while trying to dump db shcema and content, I am getting the > following error: > [najm@localhost najm]$ pg_dump -D fliprdb > flipr.sql > PQgetvalue: ERROR! tuple number 0 is out of range 0..-1 > Segmentation fault (core dumped) Hmm, looks like you've managed to expose a bug in pg_dump. It looks like pg_dump is getting an empty result to some query that it's not prepared to handle an empty result for, but there's not enough info here to tell what that query is. I'd suggest restarting the postmaster with -d2 and making sure its output is going into a logfile (don't use -S switch), then rerun pg_dump. The last query shown in the postmaster log will be the one that's causing a problem. That'll give us more info to go on. I'm thinking that the problem is something along the lines of a table with no owner (ie, no corresponding entry in pg_shadow), but can't tell for sure yet. regards, tom lane