From 97cb9a4e36ac035e1dcc108dd6d36033898ccd36 Mon Sep 17 00:00:00 2001 From: Laurenz Albe Date: Wed, 27 Aug 2025 14:10:41 +0200 Subject: [PATCH v1] Fix doc defining asynchronous replication The statement was factually wrong: WAL records can get shipped to the standby before the transaction commits. The key point is that the primary does not wait for the standby. Author: Laurenz Albe Discussion: https://postgr.es/m/175578964049.806.14564779365418625473@wrigleys.postgresql.org --- doc/src/sgml/high-availability.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b47d8b4106e..334b8a4652a 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -527,8 +527,8 @@ protocol to make nodes agree on a serializable transactional order. - It should be noted that log shipping is asynchronous, i.e., the WAL - records are shipped after transaction commit. As a result, there is a + It should be noted that log shipping is asynchronous, i.e., the primary server does + not wait until the standby receives the data. As a result, there is a window for data loss should the primary server suffer a catastrophic failure; transactions not yet shipped will be lost. The size of the data loss window in file-based log shipping can be limited by use of the -- 2.51.0