Re: Error: No one parent tuple was found

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sergio Pili <sergio(dot)pili(at)spm(dot)com(dot)ar>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error: No one parent tuple was found
Date: 2003-04-29 15:10:29
Message-ID: 26698.1051629029@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sergio Pili <sergio(dot)pili(at)spm(dot)com(dot)ar> writes:
>> psql -d colabo -c "vacuum full verbose analyze"
>> ERROR: No one parent tuple was found

AFAIK this can only happen if you have open transactions in parallel
with the VACUUM FULL. Killing off the open transactions should allow
the VACUUM to complete. See today's "Still getting VACUUM errors"
thread over in pgsql-admin.

BTW, if you cannot update to 7.3, at least update to 7.2.4 --- there are
some pretty nasty bugs in 7.2.1.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dennis Gearon 2003-04-29 15:13:08 Re: Importing from Access 2000?
Previous Message Dennis Gearon 2003-04-29 15:04:47 Re: Bug(?) with cursors using aggregate functions.