Re: [HACKERS] Finding corrupt data - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Finding corrupt data
Date
Msg-id 199912161629.LAA05501@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Finding corrupt data  (Ed Loehr <ELOEHR@austin.rr.com>)
List 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@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] pg_dump --help
Next
From: Edwin Ramirez
Date:
Subject: Oracle Compatibility (Translate function)