Note about possible data loss while canceling postgres backends. (#1414)

Note about possible data loss while canceling postgres backends.

Related to zalando#1412
This commit is contained in:
Michail Nikolaev
2020-03-10 12:08:01 +01:00
committed by GitHub
parent b020874486
commit 795efc4548
+2
View File
@@ -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 <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
-------------------------------