| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to determine a database is intact? |
| Date: | 2004-09-09 18:02:36 |
| Message-ID: | 87brgfuxqb.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Believe it or not, we haven't gotten many requests for this feature,
> partly because such corruption is so rare. Also, any checker isn't
> going to find a change from "Baker" to "Faker" in a text field.
Well there were people asking for per-block checksums. Given the frequency of
people complaining about hardware problems I'm starting to think they may be a
good idea after all.
But checksums don't detect corruption caused by software failure. That would
require a more of an fsck-like approach. There's nothing wrong with the idea,
but it would be a lot of work and nobody else has felt the need for it.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pw | 2004-09-09 19:01:20 | Where does postgres store records of DROP-ed columns? |
| Previous Message | Oleg Bartunov | 2004-09-09 17:56:59 | Re: Text Search vs MYSQL vs Lucene |