aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2010-02-20 18:28:37 +0000
committerBruce Momjian <bruce@momjian.us>2010-02-20 18:28:37 +0000
commitde9ec6543111878dcfc4f42fc0e017f5197d1c7d (patch)
tree444eab2d0d0bd0864097272a61a82b1b2a54420d
parent7363021df306885f6872d558bae8b5747c92ab3c (diff)
downloadpostgresql-de9ec6543111878dcfc4f42fc0e017f5197d1c7d.tar.gz
postgresql-de9ec6543111878dcfc4f42fc0e017f5197d1c7d.zip
Document that many solid-state drives have volatile write-back caches.
-rw-r--r--doc/src/sgml/wal.sgml5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 2c5ce011126..5f6a6eb2e18 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.61 2010/02/03 17:25:06 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.62 2010/02/20 18:28:37 momjian Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
@@ -59,7 +59,8 @@
same concerns about data loss exist for write-back drive caches as
exist for disk controller caches. Consumer-grade IDE and SATA drives are
particularly likely to have write-back caches that will not survive a
- power failure. To check write caching on <productname>Linux</> use
+ power failure. Many solid-state drives also have volatile write-back
+ caches. To check write caching on <productname>Linux</> use
<command>hdparm -I</>; it is enabled if there is a <literal>*</> next
to <literal>Write cache</>; <command>hdparm -W</> to turn off
write caching. On <productname>FreeBSD</> use