Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 9E3C7B5DBCE for ; Mon, 1 Aug 2011 12:23:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 59482-01 for ; Mon, 1 Aug 2011 15:22:56 +0000 (UTC) X-Greylist: delayed 01:45:29.266591 by SQLgrey-1.7.6 Received: from mail-gw0-f46.google.com (mail-gw0-f46.google.com [74.125.83.46]) by mail.postgresql.org (Postfix) with ESMTP id 7233EB5D800 for ; Mon, 1 Aug 2011 12:22:56 -0300 (ADT) Received: by gwaa12 with SMTP id a12so1456046gwa.19 for ; Mon, 01 Aug 2011 08:22:55 -0700 (PDT) Received: by 10.236.189.97 with SMTP id b61mr2909109yhn.482.1312205378197; Mon, 01 Aug 2011 06:29:38 -0700 (PDT) Received: from AnibalVAIO (host-5-144.a5.cmm.com.py [190.2.196.144]) by mx.google.com with ESMTPS id k8sm3678195yhm.3.2011.08.01.06.29.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 01 Aug 2011 06:29:36 -0700 (PDT) From: "Anibal David Acosta" To: Subject: synchronous_commit off Date: Mon, 1 Aug 2011 09:29:37 -0400 Message-ID: <001201cc504f$11f32e50$35d98af0$@devshock.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01CC502D.8AE314F0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AcxQTUmbo5y7VihvRAmBVWqPpVQYQg== Content-Language: es-py X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201108/9 X-Sequence-Number: 44456 This is a multipart message in MIME format. ------=_NextPart_000_0013_01CC502D.8AE314F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. Thanks ------=_NextPart_000_0013_01CC502D.8AE314F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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.

Thanks

------=_NextPart_000_0013_01CC502D.8AE314F0--