| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com> |
| 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 16:29:05 |
| Message-ID: | 199912161629.LAA05501@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tom Lane wrote:
>
> > > If there was corrupt data in a table, how would one go about finding it?
> >
> > The brute-force way is to do a SELECT * or COPY TO and see if the
> > backend survives ;-). If not, narrowing down which record is bad
> > is left as an exercise for the student...
>
> 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?
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-12-16 16:31:15 | Re: [HACKERS] pg_dump --help |
| Previous Message | Jose Soares | 1999-12-16 16:27:34 | \copy problem |