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.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us