On Tuesday, December 20, 2011 06:38:44 PM Kevin Grittner wrote: > Alvaro Herrera <alvhe...@commandprompt.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
