Strange vacuum error Was: No long-lived transaction, still can't delete tuples

At 09:56 AM 4/25/02 -0400, Tom Lane wrote:

> > BEGIN followed by select
> > (1), causes vacuum to stop with:
> > ERROR: Parent tuple was not found
>
>Oh? If you have a repeatable example of that, I'd like to see it.

OK just got a different error:
VACUUM verbose arch_ranks_arch4;
NOTICE: --Relation arch_ranks_arch4--
NOTICE: Pages 136: Changed 0, reaped 134, Empty 0, New 0; Tup 6861: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 4206, MinLen 88, MaxLen 1138; Re-using:
Free/Avail. Space 6364/2564; EndEmpty/Avail. Pages 0/23. CPU 0.01s/0.00u sec.
ERROR: No one parent tuple was found

select version();
version
---------------------------------------------------------------------
PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66

Regards,
Link.