No: The commit has the same guarantees as a synchronous commit w.r.t. data
consistency. The commit can only fail (as a whole) due to hardware problems or
postgres backend crashes.
And yes: The client commit returns, but the server can fail later and not
persist the transaction and it will be
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 o
mith
Enviado el: lunes, 01 de agosto de 2011 03:53 p.m.
Para: pgsql-performance@postgresql.org
Asunto: Re: [PERFORM] synchronous_commit off
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, c
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 di
