| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 18:13:54 |
| Message-ID: | 201112201913.54472.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, December 20, 2011 07:08:56 PM Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On Tuesday, December 20, 2011 06:38:44 PM Kevin Grittner wrote:
> >> What would you want the server to do when a page with a mismatching
> >> checksum is read?
> >
> > Follow the behaviour of zero_damaged_pages.
>
> Surely not. Nobody runs with zero_damaged_pages turned on in
> production; or at least, nobody with any semblance of a clue.
Thats my point. There is no automated solution for page errors. So it should
ERROR (not PANIC) out in normal operation and be "fixable" via
zero_damaged_pages.
I personally wouldn't even have a problem making zero_damaged_pages only
applicable in single backend mode.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-12-20 18:23:43 | Re: JSON for PG 9.2 |
| Previous Message | Tom Lane | 2011-12-20 18:08:56 | Re: Page Checksums |