Re: [HACKERS] Finding corrupt data

Bruce Momjian wrote:

> > One RDBMS I used had a utility called 'dbcheck' which did some sort of
> > examination of indices, tables, etc., and issued an 'OK' or 'CORRUPT' for
> > each examined object.  Such a utility for pgsql might simply do some
> > combination of SELECT * or COPY TO as you suggest above.
>
> Does vacuum already do that?

Not as far as I can tell.   Here's the kind of output I see from vacuum:

DEBUG:  --Relation pg_class--
DEBUG:  Pages 10: Changed 0, Reapped 1, Empty 0, New 0; Tup 695: Vac 0, Keep/VTL
0/0, Crash 0, UnUsed 35, MinLen 102, MaxLen 132; Re-using: Free/Avail. Space
3828/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index pg_class_relname_index: Pages 16; Tuples 695: Deleted 0. Elapsed
0/0 sec.
DEBUG:  Index pg_class_oid_index: Pages 7; Tuples 695: Deleted 0. Elapsed 0/0
sec.

Am I missing something?

Cheers,
Ed Loehr