From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Page Checksums |
Date: | 2011-12-19 14:14:09 |
Message-ID: | 20111219141409.GA24234@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Aidan Van Dyk (aidan(at)highrise(dot)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?
Perhaps that's a stretch, but if we can figure out that a page is torn
already, then perhaps it's not so far fetched..
Thanks,
Stephen
(who is no expert on WAL/torn pages/etc)
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2011-12-19 14:18:21 | Re: Page Checksums |
Previous Message | Greg Smith | 2011-12-19 14:06:54 | Re: archive_keepalive_command |