Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitde9ec65

Browse files
committed
Document that many solid-state drives have volatile write-back caches.
1 parent7363021 commitde9ec65

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎doc/src/sgml/wal.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.61 2010/02/03 17:25:06 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.62 2010/02/20 18:28:37 momjian Exp $ -->
22

33
<chapter id="wal">
44
<title>Reliability and the Write-Ahead Log</title>
@@ -59,7 +59,8 @@
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. To check write caching on <productname>Linux</> use
62+
power failure. Many solid-state drives also have volatile write-back
63+
caches. To check write caching on <productname>Linux</> use
6364
<command>hdparm -I</>; it is enabled if there is a <literal>*</> next
6465
to <literal>Write cache</>; <command>hdparm -W</> to turn off
6566
write caching. On <productname>FreeBSD</> use

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp