X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8D36ED1C9F2 for ; Fri, 30 Jan 2004 09:49:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 39498-02 for ; Fri, 30 Jan 2004 05:49:21 -0400 (AST) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id D6A97D1CA5E for ; Fri, 30 Jan 2004 05:49:17 -0400 (AST) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0U9r8p01186; Fri, 30 Jan 2004 10:53:09 +0100 Received: from bigfoot.com (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0U9YUR20472; Fri, 30 Jan 2004 10:34:30 +0100 Message-ID: <401A2831.10005@bigfoot.com> Date: Fri, 30 Jan 2004 10:47:29 +0100 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031206 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane , "pgsql-admin@postgresql.org" Subject: Re: commit after dead lock References: <4019A484.5010509@bigfoot.com> <20040129170739.U35951@megazone.bigpanda.com> <3460.1075434630@sss.pgh.pa.us> In-Reply-To: <3460.1075434630@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/291 X-Sequence-Number: 12154 Tom Lane wrote: > Stephan Szabo writes: > >>It's not really any different than other errors. The commit doesn't >>complain (although it also doesn't actually commit anything). > > > People have occasionally suggested that the command tag from a COMMIT > should read "ABORT" or "ROLLBACK" if the transaction was previously > aborted. I don't have a strong feeling about it one way or the other. > It'd clearly be helpful for human users, but I could see it confusing > programs that expect the existing behavior of command tag always > matching command. Well, I agree but I think that is better at least rise a warning. regards Geetano Mendola