From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/wal-intro.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/wal-intro.html') diff --git a/doc/src/sgml/html/wal-intro.html b/doc/src/sgml/html/wal-intro.html index 193c265..1991edb 100644 --- a/doc/src/sgml/html/wal-intro.html +++ b/doc/src/sgml/html/wal-intro.html @@ -1,5 +1,5 @@ -30.3. Write-Ahead Logging (WAL)
30.3. Write-Ahead Logging (WAL)
Prev UpChapter 30. Reliability and the Write-Ahead LogHome Next

30.3. Write-Ahead Logging (WAL)

+30.3. Write-Ahead Logging (WAL)

30.3. Write-Ahead Logging (WAL)
Prev UpChapter 30. Reliability and the Write-Ahead LogHome Next

30.3. Write-Ahead Logging (WAL)

Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about @@ -45,4 +45,4 @@ of the database state — if it is made over some period of time, then replaying the WAL log for that period will fix any internal inconsistencies. -

Prev Up Next
30.2. Data Checksums Home 30.4. Asynchronous Commit
\ No newline at end of file +

Prev Up Next
30.2. Data Checksums Home 30.4. Asynchronous Commit
\ No newline at end of file -- cgit v1.2.3