mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-21 08:29:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

README comments on checksums on page holes.

Browse Source
This commit is contained in:
Simon Riggs 2013-04-08 08:42:52 +01:00
parent 1be203519a
commit a4b94b8515
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/backend/storage/page/README
View File

@ -44,6 +44,17 @@ record a full page image in WAL. Hint bits updates should be protected using
MarkBufferDirtyHint(), which is responsible for writing the full-page image MarkBufferDirtyHint(), which is responsible for writing the full-page image
when necessary. when necessary.
Note that when we write a page checksum we include the hopefully zero bytes
that form the hole in the centre of a standard page. Thus, when we read the
block back from storage we implicitly check that the hole is still all zeroes.
We do this to ensure that we spot errors that could have destroyed data even
if they haven't actually done so. Full page images stored in WAL do *not*
check that the hole is all zero; the data in the hole is simply skipped and
re-zeroed if the backup block is reapplied. We do this because a failure in
WAL is a fatal error and prevents further recovery, whereas a checksum failure
on a normal data block is a hard error but not a critical one for the server,
even if it is a very bad thing for the user.
New WAL records cannot be written during recovery, so hint bits set during New WAL records cannot be written during recovery, so hint bits set during
recovery must not dirty the page if the buffer is not already dirty, when recovery must not dirty the page if the buffer is not already dirty, when
checksums are enabled. Systems in Hot-Standby mode may benefit from hint bits checksums are enabled. Systems in Hot-Standby mode may benefit from hint bits