| From: | Jack Orenstein <jao(at)geophile(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Detecting database corruption |
| Date: | 2004-01-13 23:06:03 |
| Message-ID: | 400479DB.60601@geophile.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
My company is developing a PostgreSQL 7.4 application. We don't want
our customers to have to manage the database. If the database ever
becomes corrupt, we have procedures for restoring the database from
backup data. The question we've been wondering about is how to detect
a corrupt database. False positives are acceptable (database isn't
really corrupt but we think it is); false negatives are not, (database
is corrupt but we can't tell).
- Are any cases of corruption detected in the normal operation of
PostgreSQL?
- If there are, then how are applications notified when corruption
is detected?
- What symptoms should prompt us to suspect and check for corruption?
- Are there any tools we can run to determine whether a database is
corrupt?
Jack Orenstein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Campaigne | 2004-01-13 23:12:48 | Incremental Development |
| Previous Message | Nigel J. Andrews | 2004-01-13 23:00:03 | Re: Drawbacks of using BYTEA for PK? |