Skip site navigation (1) Skip section navigation (2)

Re: commit after dead lock

From: Gaetano Mendola <mendola(at)bigfoot(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: commit after dead lock
Date: 2004-01-30 09:47:29
Message-ID: 401A2831.10005@bigfoot.com (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane wrote:

> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)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.


Well, I agree but I think that is better at least rise a
warning.


regards
Geetano Mendola


In response to

pgsql-admin by date

Next:From: Trevor AstropeDate: 2004-01-30 14:48:28
Subject: Veritas Filesystem
Previous:From: supiahDate: 2004-01-30 09:41:57
Subject: Error during installation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group