From: Bruce Momjian Date: Mon, 10 Dec 2007 14:51:10 +0000 (+0000) Subject: Write cache doc cleanups X-Git-Tag: REL8_3_RC1~109 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3e113efdf06e1f8b5e4a89b2bdccf36d48217698;p=postgresql Write cache doc cleanups Greg Smith --- diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 55cd6b1d6b..2d0886334a 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ - + Reliability and the Write-Ahead Log @@ -57,11 +57,11 @@ And finally, most disk drives have caches. Some are write-through while some are write-back, and the same concerns about data loss exist for write-back drive caches as - exist for disk controller caches. Consumer-grade IDE drives are + 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 Linux use hdparm -I; it is enabled if there is a * next - to Write cache. hdparm -W can to turn off + to Write cache. hdparm -W to turn off write caching. On FreeBSD use atacontrol. (For SCSI disks use sdparm