| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Christopher Browne" <cbbrowne(at)gmail(dot)com> |
| Cc: | "greg" <greg(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Page Checksums |
| Date: | 2011-12-20 17:38:44 |
| Message-ID: | 4EF073C40200002500043E86@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Christopher Browne's message of mar dic 20 14:12:56
> -0300 2011:
>
>> It's not evident which problems will be "real" ones. And in such
>> cases, is the answer to turf the database and recover from
>> backup, because of a single busted page? For a big database, I'm
>> not sure that's less scary than the possibility of one page
>> having a corruption.
>
> I don't think the problem is having one page of corruption. The
> problem is *not knowing* that random pages are corrupted, and
> living in the fear that they might be.
What would you want the server to do when a page with a mismatching
checksum is read?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-12-20 17:40:56 | Re: Page Checksums |
| Previous Message | Kevin Grittner | 2011-12-20 17:36:32 | Re: Page Checksums |