Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit adfb444

Browse files
committed
Document ATAPI drive flush command, and mention SSD drives.
1 parent 4b0f822 commit adfb444

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

doc/src/sgml/wal.sgml

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.62 2010/02/20 18:28:37 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.63 2010/02/27 01:39:46 momjian Exp $ -->
22

33
<chapter id="wal">
44
<title>Reliability and the Write-Ahead Log</title>
@@ -59,8 +59,11 @@
5959
same concerns about data loss exist for write-back drive caches as
6060
exist for disk controller caches. Consumer-grade IDE and SATA drives are
6161
particularly likely to have write-back caches that will not survive a
62-
power failure. Many solid-state drives also have volatile write-back
63-
caches. To check write caching on <productname>Linux</> use
62+
power failure, though <acronym>ATAPI-6</> introduced a drive cache
63+
flush command that some file systems use, e.g. <acronym>ZFS</>.
64+
Many solid-state drives also have volatile write-back
65+
caches, and many do not honor cache flush commands by default.
66+
To check write caching on <productname>Linux</> use
6467
<command>hdparm -I</>; it is enabled if there is a <literal>*</> next
6568
to <literal>Write cache</>; <command>hdparm -W</> to turn off
6669
write caching. On <productname>FreeBSD</> use

0 commit comments

Comments
 (0)