Date: Sat, 11 May 2002 17:39:40 -0500 (CDT)
From: Brian McCane <bmccane@mccons.net>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: VACUUM FULL 
In-Reply-To: <20020511120040.X12454-100000@fw.mccons.net>
Message-ID: <20020511173322.J37676-100000@fw.mccons.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


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

What does this mean?  Can I fix it without a full dump/restore?  Where did
it come from?  All these questions and many more are begging for an
answer.  One of the tables has 38 foreign key references to its primary
key, the other has 12.  Only a couple of the other tables even have a
reference.  This may not have anything to do with the problem, it is just
an observation.

Anyway, any help in fixing this would be greatly appreciated.  I have
already had the site half way down for almost 3 days because of the VACUUM
FULL on the big table, so I would prefer not to spend a couple of days
doing a dump/restore.  Could I dump the tables, disable their triggers,
truncate them, restore the data, and re-enable the triggers?

- brian

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"