From 542db9e02f5aaafe4c831797133acb1aff5d7828 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Thu, 4 Sep 2025 10:22:08 +0900 Subject: [PATCH] doc: Remove confusing sentence about async log shipping The original sentence is old, as of 5e550acbc4d1, referring to a dependency with transaction commit and the timing of the records flushed, which may not be always true. Reported-by: Artem Gavrilov Reviewed-by: Laurenz Albe Reviewed-by: Robert Treat Discussion: https://postgr.es/m/175578964049.806.14564779365418625473@wrigleys.postgresql.org --- doc/src/sgml/high-availability.sgml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b47d8b4106ef..ffeff3f2b247 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -527,9 +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 - window for data loss should the primary server suffer a catastrophic + It should be noted that log shipping is asynchronous. 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 archive_timeout parameter, which can be set as low -- 2.51.0