diff options
| author | Simon Riggs <simon@2ndQuadrant.com> | 2013-03-19 08:57:29 +0000 |
|---|---|---|
| committer | Simon Riggs <simon@2ndQuadrant.com> | 2013-03-19 08:57:29 +0000 |
| commit | 1a091002cfa2180a908b36d56c58749a175b4be7 (patch) | |
| tree | c47afaa9748f43d8f7945df2efc7ea566a1dd950 | |
| parent | 8c3b87ca10a54daf06e41986d763e12538c06ab9 (diff) | |
| download | postgresql-1a091002cfa2180a908b36d56c58749a175b4be7.tar.gz postgresql-1a091002cfa2180a908b36d56c58749a175b4be7.zip | |
Clarify assumption of filesystem metadata integrity.
Jeff Davis
| -rw-r--r-- | doc/src/sgml/wal.sgml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index e96f0ce17d5..b1784e5cb3a 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -148,8 +148,9 @@ there is little it can do to make sure the data has arrived at a truly non-volatile storage area. Rather, it is the administrator's responsibility to make certain that all storage components - ensure data integrity. Avoid disk controllers that have non-battery-backed - write caches. At the drive level, disable write-back caching if the + ensure integrity for both data and filesystem metadata. + Avoid disk controllers that have non-battery-backed write caches. + At the drive level, disable write-back caching if the drive cannot guarantee the data will be written before shutdown. If you use SSDs, be aware that many of these do not honor cache flush commands by default. |