aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/wal.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 9e9489da156..17d82c71af2 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.63 2010/02/27 01:39:46 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.64 2010/02/27 20:16:17 momjian Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
@@ -60,7 +60,7 @@
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, though <acronym>ATAPI-6</> introduced a drive cache
- flush command that some file systems use, e.g. <acronym>ZFS</>.
+ flush command (FLUSH CACHE EXT) that some file systems use, e.g. <acronym>ZFS</>.
Many solid-state drives also have volatile write-back
caches, and many do not honor cache flush commands by default.
To check write caching on <productname>Linux</> use