Thread: vacuum failure...

I've got a problem vacuuming a table and can't seem to find a way to 
fix it...

vacuum full verbose analyze folders;
NOTICE:  --Relation folders--
NOTICE:  Pages 18598: Changed 0, reaped 18598, Empty 0, New 0; Tup 
69849: Vac 0, Keep/VTL 0/0, UnUsed 1870572, MinLen 64, MaxLen 88; Re-
using: Free/Avail. Space 139159408/139159408; EndEmpty/Avail. Pages 
0/18598.       CPU 0.34s/0.09u sec elapsed 0.51 sec.
ERROR:  No one parent tuple was found

-Michael
_________________________________________________________________   http://fastmail.ca/ - Fast Secure Web Email for
Canadians

"Michael Richards" <michael@fastmail.ca> writes:
> ERROR:  No one parent tuple was found

Postgres version?

AFAIR, all known causes of this are fixed in 7.2.4.
        regards, tom lane

> "Michael Richards" <michael@fastmail.ca> writes:
>> ERROR:  No one parent tuple was found
> 
> Postgres version?
> 
> AFAIR, all known causes of this are fixed in 7.2.4.

Oops, sorry:                              version                               
---------------------------------------------------------------------PostgreSQL 7.2.3 on i386-unknown-freebsd4.5,
compiledby GCC 2.95.3
 

If I upgrade to 7.2.4 will that fix the problem or just fix a bug 
that would cause that problem? 

-Michael
_________________________________________________________________   http://fastmail.ca/ - Fast Secure Web Email for
Canadians

"Michael Richards" <michael@fastmail.ca> writes:
> If I upgrade to 7.2.4 will that fix the problem or just fix a bug 
> that would cause that problem? 

It should make the problem go away --- the on-disk configuration is
legitimate, it's just VACUUM that's getting confused.  (Unless you
have some new variant of this issue that we haven't seen before.)
        regards, tom lane