aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2020-03-26 15:05:54 +0100
committerMagnus Hagander <magnus@hagander.net>2020-03-26 15:05:54 +0100
commiteff5b245df259c73d8342e2f04dba5a832d2ea0a (patch)
tree00205c6433e25b590a5550ae179c9437115bc07e
parent49bf81536e242f079bfbce6e8f95f53f18207dd5 (diff)
downloadpostgresql-eff5b245df259c73d8342e2f04dba5a832d2ea0a.tar.gz
postgresql-eff5b245df259c73d8342e2f04dba5a832d2ea0a.zip
Document that pg_checksums exists in checksums README
Author: Daniel Gustafsson <daniel@yesql.se>
-rw-r--r--src/backend/storage/page/README3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/storage/page/README b/src/backend/storage/page/README
index 5127d98da37..4e45bd92abc 100644
--- a/src/backend/storage/page/README
+++ b/src/backend/storage/page/README
@@ -9,7 +9,8 @@ have a very low measured incidence according to research on large server farms,
http://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf, discussed
2010/12/22 on -hackers list.
-Current implementation requires this be enabled system-wide at initdb time.
+Current implementation requires this be enabled system-wide at initdb time, or
+by using the pg_checksums tool on an offline cluster.
The checksum is not valid at all times on a data page!!
The checksum is valid when the page leaves the shared pool and is checked