Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id D8A32476026 for ; Sun, 12 May 2002 13:50:09 -0400 (EDT) Received: from fw.mccons.net (adsl-65-64-105-41.dsl.kscymo.swbell.net [65.64.105.41]) by postgresql.org (Postfix) with ESMTP id 09FCA475F99 for ; Sun, 12 May 2002 13:49:44 -0400 (EDT) Received: (from root@localhost) by fw.mccons.net (8.11.3/8.11.4) id g4CHnie04728; Sun, 12 May 2002 12:49:44 -0500 (CDT) (envelope-from bmccane@mccons.net) Received: from localhost (localhost [127.0.0.1]) by fw.mccons.net (8.11.3/8.11.4av) with ESMTP id g4CHnZc04312; Sun, 12 May 2002 12:49:35 -0500 (CDT) (envelope-from bmccane@mccons.net) Date: Sun, 12 May 2002 12:49:35 -0500 (CDT) From: Brian McCane To: Tom Lane Cc: pgsql-admin Subject: Re: VACUUM FULL In-Reply-To: <178.1021219490@sss.pgh.pa.us> Message-ID: <20020512124637.E81191-100000@fw.mccons.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 X-Razor-Spam-ID: cd71c043a564cc2b539fbd0dba0a07dd0b7d6ccb X-Archive-Number: 200205/104 X-Sequence-Number: 4279 Tom, I was going to do a pg_ctl stop/start cycle to try to fix the error, however.... What do I need to do to debug? I am on FreeBSD 5.0. I assume I can use GDB to connect to a running backend, but have not done any serious debugging in gdb for 4-5 years. If it is too ugly, I might consider allowing someone into the machine, but it doesn't make me excited to contemplate it. - brian On Sun, 12 May 2002, Tom Lane wrote: > > Brian McCane writes: > > Okay, now I am a little scared. Before I started rebuilding indexes, I > > decided to do the VACUUM FULL thing on all of my tables. On my two most > > referenced tables I am getting: > > > ERROR: No one parent tuple was found > > Oh, that's interesting. We've gotten sporadic reports of that error > message but no one's ever submitted a reproducible case. Don't suppose > you want to trace through VACUUM FULL with a debugger (or let someone > else do so) to see why it's getting confused? > > FWIW, I don't think you need fear data loss. VACUUM FULL has some, um, > quite baroque code to deal with moving update chains as a unit, and it's > just reporting that it couldn't figure out how to move what looked like > a tuple chain. > > AFAIK this situation can only occur when there are open transactions > that can still see some already-replaced tuple. So the error would > probably go away if you closed all your open transactions. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > Wm. Brian McCane | Life is full of doors that won't open Search http://recall.maxbaud.net/ | when you knock, equally spaced amid those Usenet http://freenews.maxbaud.net/ | that open when you don't want them to. Auction http://www.sellit-here.com/ | - Roger Zelazny "Blood of Amber"