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 67089D1B449 for ; Fri, 30 Jan 2004 03:51:03 +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 43245-09 for ; Thu, 29 Jan 2004 23:50:35 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E1866D1B44D for ; Thu, 29 Jan 2004 23:50:30 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0U3oUbq003461; Thu, 29 Jan 2004 22:50:31 -0500 (EST) To: Stephan Szabo Cc: Gaetano Mendola , "pgsql-admin@postgresql.org" Subject: Re: commit after dead lock In-reply-to: <20040129170739.U35951@megazone.bigpanda.com> References: <4019A484.5010509@bigfoot.com> <20040129170739.U35951@megazone.bigpanda.com> Comments: In-reply-to Stephan Szabo message dated "Thu, 29 Jan 2004 17:11:07 -0800" Date: Thu, 29 Jan 2004 22:50:30 -0500 Message-ID: <3460.1075434630@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/289 X-Sequence-Number: 12152 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. regards, tom lane