| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, Vadim Mikheev <vmikheev(at)SECTORBASE(dot)COM> |
| Subject: | Re: Database corruption? |
| Date: | 2001-10-30 16:03:13 |
| Message-ID: | 20715.1004457793@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> The problem ended up being bad RAM (it was good two weeks ago). I don't
> think it's of any use to do anything else with the database.
Ah so. Thanks for following up.
It may be unthinkable hubris to say this, but ... I am starting to
notice that a larger and larger fraction of serious trouble reports
ultimately trace to hardware failures, not software bugs. Seems we've
done a good job getting data-corruption bugs out of Postgres.
Perhaps we should reconsider the notion of keeping CRC checksums on
data pages. Not sure what we could do to defend against bad RAM,
however.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-30 16:04:36 | Re: INNER JOINS in 7.0.3 & 7.1.3 |
| Previous Message | Alvaro Herrera | 2001-10-30 15:51:15 | Re: Database corruption? |