From 9295eea8391abaa1f5ecaa50cc39c4e8165f74b4 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 27 Feb 2010 20:16:17 +0000
Subject: Document ATAPI FLUSH CACHE EXT.

---
 doc/src/sgml/wal.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc/src')

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
-- 
cgit v1.2.3