Re: Synchronous commit behavior during network outage
От | Aleksander Alekseev |
---|---|
Тема | Re: Synchronous commit behavior during network outage |
Дата | |
Msg-id | CAJ7c6TNp=9STwXX_1Rvp+OpszHqtMKXqUJcAXwgz9w95P8J56Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Synchronous commit behavior during network outage (Tomas Vondra <tomas.vondra@enterprisedb.com>) |
Список | pgsql-hackers |
Hi Timas, > > Thanks for the report. It seems to be a clear violation of what is > > promised in the docs. Although it's unlikely that someone implemented > > an application which deals with important data and "pressed Ctr+C" as > > it's done in psql. So this might be not such a critical issue after > > all. BTW what version of PostgreSQL are you using? > > > > Which part of the docs does this contradict? The documentation to synchronous_commit = remote_apply explicitly states [1]: """ When set to remote_apply, commits will wait until replies from the current synchronous standby(s) indicate they have received the commit record of the transaction and applied it, so that it has become visible to queries on the standby(s), and also written to durable storage on the standbys. """ Here commit on the master happened before receiving replies from the standby(s). [1]: https://www.postgresql.org/docs/13/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT -- Best regards, Aleksander Alekseev
В списке pgsql-hackers по дате отправления: