From 795efc4548e22a5f44603c996a8c373a4d778fd2 Mon Sep 17 00:00:00 2001 From: Michail Nikolaev Date: Tue, 10 Mar 2020 14:08:01 +0300 Subject: [PATCH] Note about possible data loss while canceling postgres backends. (#1414) Note about possible data loss while canceling postgres backends. Related to zalando#1412 --- docs/replication_modes.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/replication_modes.rst b/docs/replication_modes.rst index b6dfe1d0..9446c5a2 100644 --- a/docs/replication_modes.rst +++ b/docs/replication_modes.rst @@ -57,6 +57,8 @@ You can ensure that a standby never becomes the synchronous standby by setting ` Synchronous mode can be switched on and off via Patroni REST interface. See :ref:`dynamic configuration ` for instructions. +Note: Because of the way synchronous replication is implemented in PostgreSQL it is still possible to lose transactions even when using ``synchronous_mode_strict``. If the PostgreSQL backend is cancelled while waiting to acknowledge replication (as a result of packet cancellation due to client timeout or backend failure) transaction changes become visible for other backends. Such changes are not yet replicated and may be lost in case of standby promotion. + Synchronous mode implementation -------------------------------