Re: Read consistency when using synchronous_commit=off
| От | Fabio Pardi |
|---|---|
| Тема | Re: Read consistency when using synchronous_commit=off |
| Дата | |
| Msg-id | 5609bb8f-ee85-5e1b-9cb3-7a4ec5458f81@portavita.eu обсуждение исходный текст |
| Ответ на | Read consistency when using synchronous_commit=off (pshadangi <pshadangi@gmail.com>) |
| Ответы |
Re: Read consistency when using synchronous_commit=off
|
| Список | pgsql-general |
Hi,
all clients will get the latest version of the row (from RAM, that is). The only thing is that in case of server crash, not-yet-written-to-disk commits will be lost.
detailed explanation can be found here:
https://www.postgresql.org/docs/current/wal-async-commit.html
regards,
fabio pardi
all clients will get the latest version of the row (from RAM, that is). The only thing is that in case of server crash, not-yet-written-to-disk commits will be lost.
detailed explanation can be found here:
https://www.postgresql.org/docs/current/wal-async-commit.html
regards,
fabio pardi
On 15/01/2019 11:58, pshadangi wrote:
To improve commit performance we are planning to use "synchronous_commit=off", with this if multiple clients are reading the same data/row will they always get the latest updated data/row ? (clients are using committed read and we are not using clustered environment, we have just one instance of postgres serving local clients running on the same machine).
For example if client1 updates a row then the updated value is available to client2 immediately after the commit or there is a delay as commit is now asynchronous ?
В списке pgsql-general по дате отправления: