Re: Page Checksums - Mailing list pgsql-hackers

From David Fetter
Subject Re: Page Checksums
Date
Msg-id 20111219170700.GA29634@fetter.org
Whole thread Raw
In response to Re: Page Checksums  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Page Checksums  (Stephen Frost <sfrost@snowman.net>)
Re: Page Checksums  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Dec 19, 2011 at 09:34:51AM -0500, Robert Haas wrote:
> On Mon, Dec 19, 2011 at 9:14 AM, Stephen Frost <sfrost@snowman.net> wrote:
> > * Aidan Van Dyk (aidan@highrise.ca) wrote:
> >> But the scary part is you don't know how long *ago* the crash was.
> >> Because a hint-bit-only change w/ a torn-page is a "non event" in
> >> PostgreSQL *DESIGN*, on crash recovery, it doesn't do anything to try
> >> and "scrub" every page in the database.
> >
> > Fair enough, but, could we distinguish these two cases?  In other words,
> > would it be possible to detect if a page was torn due to a 'traditional'
> > crash and not complain in that case, but complain if there's a CRC
> > failure and it *doesn't* look like a torn page?
>
> No.

Would you be so kind as to elucidate this a bit?

Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe
Next
From: Nikhil Sontakke
Date:
Subject: Re: Review: Non-inheritable check constraints