Re: commit after dead lock - Mailing list pgsql-admin

From Tom Lane
Subject Re: commit after dead lock
Date
Msg-id 3460.1075434630@sss.pgh.pa.us
Whole thread Raw
In response to Re: commit after dead lock  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Responses Re: commit after dead lock  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-admin
Stephan Szabo <sszabo@megazone.bigpanda.com> 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

pgsql-admin by date:

Previous
From: Andrew Rawnsley
Date:
Subject: Re: Forcing connections closed
Next
From: Thierry Missimilly
Date:
Subject: Re: Help: System requirements for postgresql 7.4.1