| From: | Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthew Hagerty <matthew(at)venux(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Finding corrupt data |
| Date: | 1999-12-16 17:29:32 |
| Message-ID: | 3859217B.9C3A338B@austin.rr.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-12-16 17:31:10 | Re: [HACKERS] Finding corrupt data |
| Previous Message | Bruce Momjian | 1999-12-16 16:31:15 | Re: [HACKERS] pg_dump --help |