From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/wal-reliability.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src/sgml/html/wal-reliability.html') diff --git a/doc/src/sgml/html/wal-reliability.html b/doc/src/sgml/html/wal-reliability.html index 84505e3..f80688a 100644 --- a/doc/src/sgml/html/wal-reliability.html +++ b/doc/src/sgml/html/wal-reliability.html @@ -1,5 +1,5 @@ -30.1. Reliability
30.1. Reliability
Prev UpChapter 30. Reliability and the Write-Ahead LogHome Next

30.1. Reliability

+30.1. Reliability

30.1. Reliability
Prev UpChapter 30. Reliability and the Write-Ahead LogHome Next

30.1. Reliability

Reliability is an important property of any serious database system, and PostgreSQL does everything possible to guarantee reliable operation. One aspect of reliable operation is @@ -57,7 +57,7 @@ to disable it.

  • On FreeBSD, IDE drives can be queried using - atacontrol and write caching turned off using + camcontrol identify and write caching turned off using hw.ata.wc=0 in /boot/loader.conf; SCSI drives can be queried using camcontrol identify, and the write cache both queried and changed using @@ -158,4 +158,4 @@ PostgreSQL does not protect against correctable memory errors and it is assumed you will operate using RAM that uses industry standard Error Correcting Codes (ECC) or better protection. -

    • Prev Up Next
    Chapter 30. Reliability and the Write-Ahead Log Home 30.2. Data Checksums
    \ No newline at end of file +

    Prev Up Next
    Chapter 30. Reliability and the Write-Ahead Log Home 30.2. Data Checksums
    \ No newline at end of file -- cgit v1.2.3