mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
Document ATAPI drive flush command, and mention SSD drives.
This commit is contained in:
parent
4b0f822c77
commit
adfb444581
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.62 2010/02/20 18:28:37 momjian Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.63 2010/02/27 01:39:46 momjian Exp $ -->
|
||||||
|
|
||||||
<chapter id="wal">
|
<chapter id="wal">
|
||||||
<title>Reliability and the Write-Ahead Log</title>
|
<title>Reliability and the Write-Ahead Log</title>
|
||||||
@ -59,8 +59,11 @@
|
|||||||
same concerns about data loss exist for write-back drive caches as
|
same concerns about data loss exist for write-back drive caches as
|
||||||
exist for disk controller caches. Consumer-grade IDE and SATA 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
|
particularly likely to have write-back caches that will not survive a
|
||||||
power failure. Many solid-state drives also have volatile write-back
|
power failure, though <acronym>ATAPI-6</> introduced a drive cache
|
||||||
caches. To check write caching on <productname>Linux</> use
|
flush command 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
|
||||||
<command>hdparm -I</>; it is enabled if there is a <literal>*</> next
|
<command>hdparm -I</>; it is enabled if there is a <literal>*</> next
|
||||||
to <literal>Write cache</>; <command>hdparm -W</> to turn off
|
to <literal>Write cache</>; <command>hdparm -W</> to turn off
|
||||||
write caching. On <productname>FreeBSD</> use
|
write caching. On <productname>FreeBSD</> use
|
||||||
|
Loading…
Reference in New Issue
Block a user