| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | greg(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Page Checksums |
| Date: | 2011-12-20 13:36:27 |
| Message-ID: | CA+Tgmoau8hcHgZe0jrvp0eM4+DzzLTagt692SiOdo0ehpbx2Bw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 19, 2011 at 2:44 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I was thinking that we would warn when such was found, set hint bits
> as needed, and rewrite with the new CRC. In the unlikely event that
> it was a torn hint-bit-only page update, it would be a warning about
> something which is a benign side-effect of the OS or hardware crash.
But that's terrible. Surely you don't want to tell people:
WARNING: Your database is corrupted, or maybe not. But don't worry,
I modified the data block so that you won't get this warning again.
OK, I guess I'm not sure that you don't want to tell people that. But
*I* don't!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-12-20 13:38:21 | Re: sync_seqscans in postgresql.conf |
| Previous Message | Andrew Dunstan | 2011-12-20 13:36:14 | Re: pgstat wait timeout |