| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Christopher Browne" <cbbrowne(at)gmail(dot)com>, "greg" <greg(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Page Checksums |
| Date: | 2011-12-20 17:40:56 |
| Message-ID: | 201112201840.56440.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, December 20, 2011 06:38:44 PM Kevin Grittner wrote:
> 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?
Follow the behaviour of zero_damaged_pages.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-12-20 17:44:48 | Re: Page Checksums |
| Previous Message | Kevin Grittner | 2011-12-20 17:38:44 | Re: Page Checksums |