Re: [BUGS] BUG #1118: Misleading Commit message - Mailing list pgsql-hackers

From elein
Subject Re: [BUGS] BUG #1118: Misleading Commit message
Date
Msg-id 20040710135622.A6381@cookie.varlena.com
Whole thread Raw
In response to Re: [BUGS] BUG #1118: Misleading Commit message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] BUG #1118: Misleading Commit message
List pgsql-hackers
FYI: I'm agreeing w/Tom who is agreeing with me.

The tag change should be good.  I do hope people are
not relying on seeing COMMIT when the transaction
rolled back.  It does not seem that in this case
they would.

elein

On Sat, Jul 10, 2004 at 04:13:49PM -0400, Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > As I remember, the big issue was how often applications are looking and
> > comparing these tags to take actions.  I think we should return ROLLBACK
> > on COMMIT failure and we can see if we get any problem reports during
> > beta.
> 
> Good enough; I'll make it happen.
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Nested Transactions, Abort All
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #1118: Misleading Commit message