From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Renê Salomão <rene(at)ibiz(dot)com(dot)br> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ERROR: No one parent tuple was found |
Date: | 2003-01-20 15:52:32 |
Message-ID: | 3371.1043077952@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?ISO-8859-1?Q?Ren=EA_Salom=E3o?= <rene(at)ibiz(dot)com(dot)br> writes:
> After run "VACCUM FULL VERBOSE ANALYZE" the following message appears:
> "ERROR: No one parent tuple was found"...
> What can be causing this problem?
> Running a Pg 7.2.3 on Mandrake 8.1
This is a known problem which is fixed in 7.3. I believe in 7.2 you can
make the error go away by doing "SELECT * FROM table FOR UPDATE" --- but
it might come back again. (VACUUM gets confused by some scenarios
involving aborted SELECT FOR UPDATE commands; see the pghackers archives
from last August or so for details.)
IIRC, Red Hat has back-patched the 7.3 fix into their latest 7.2.3-based
release, but it was never back-patched in community sources.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-20 15:57:09 | Re: passwords and 7.3 |
Previous Message | Chris Boget | 2003-01-20 15:51:32 | Re: Altering a table - positioning new columns |