Re: synchronous_commit off
| От | Greg Smith |
|---|---|
| Тема | Re: synchronous_commit off |
| Дата | |
| Msg-id | 4E37040D.8000000@2ndQuadrant.com обсуждение исходный текст |
| Ответ на | synchronous_commit off ("Anibal David Acosta" <aa@devshock.com>) |
| Ответы |
Re: synchronous_commit off
Re: synchronous_commit off |
| Список | pgsql-performance |
On 08/01/2011 09:29 AM, Anibal David Acosta wrote:
No. You are turning off the wait for the transaction to hit disk before returning to the client, but all the validation checks are done before that. The sole risk with synchronous_commit off is that a client will get COMMIT, but the server will lose the transaction completely--when there's a crash before it's written to disk.
Can a transaction committed asynchronously report an error, duplicate key or something like that, causing a client with a OK transaction but server with a FAILED transaction.
No. You are turning off the wait for the transaction to hit disk before returning to the client, but all the validation checks are done before that. The sole risk with synchronous_commit off is that a client will get COMMIT, but the server will lose the transaction completely--when there's a crash before it's written to disk.
-- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
В списке pgsql-performance по дате отправления: