Thread: Postgres problems

Postgres problems

From
"Christopher Kings-Lynne"
Date:
OK,

I seem to have recovered from my Postgres probs.  I decided to do a vacuum
full to clean things up.  I got this about halfway through:

usa=# vacuum full analyze;
ERROR:  No one parent tuple was found

Log:

2002-08-28 19:38:47 DEBUG:  Index expiry_users_users_key: Pages 110; Tuples
41310: Deleted 866.       CPU 0.04s/0.03u sec elapsed 1.99 sec.
2002-08-28 19:38:54 DEBUG:  Index users_users_email_lower_idx: Pages 269;
Tuples 41310: Deleted 866.       CPU 0.09s/0.08u sec elapsed 6.75 sec.
2002-08-28 19:39:25 ERROR:  No one parent tuple was found

Any fix for that?

Chris



Re: Postgres problems

From
Tom Lane
Date:
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> I seem to have recovered from my Postgres probs.  I decided to do a vacuum
> full to clean things up.  I got this about halfway through:

> usa=# vacuum full analyze;
> ERROR:  No one parent tuple was found

> Any fix for that?

Try a "SELECT * FROM <table> FOR UPDATE" outside any transaction block.
That should clear the problem and let you vacuum.  This is fixed in CVS
tip but there's no fix in 7.2.2.
        regards, tom lane