From: Craig Ringer <craig@postnewspapers.com.au>
To: Greg Smith <greg@2ndQuadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: synchronous_commit off
Date: Tue, 02 Aug 2011 07:49:11 +0800
Message-ID: <4E373B77.8060001@postnewspapers.com.au> (raw)
In-Reply-To: <4E37040D.8000000@2ndQuadrant.com>
References: <001201cc504f$11f32e50$35d98af0$@devshock.com>
<4E37040D.8000000@2ndQuadrant.com>
On 2/08/2011 3:52 AM, Greg Smith wrote:
> On 08/01/2011 09:29 AM, Anibal David Acosta wrote:
>>
>> 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.
What about an I/O error during write, or other HW-level issues that
might cause a transaction to fail to commit while others proceed fine?
--
Craig Ringer
POST Newspapers
276 Onslow Rd, Shenton Park
Ph: 08 9381 3088 Fax: 08 9388 2258
ABN: 50 008 917 717
http://www.postnewspapers.com.au/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: craig@postnewspapers.com.au, greg@2ndQuadrant.com
Subject: Re: synchronous_commit off
In-Reply-To: <4E373B77.8060001@postnewspapers.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox