Re: [BUGS] BUG #1118: Misleading Commit message

From: elein <elein(at)varlena(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, elein <elein(at)varlena(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #1118: Misleading Commit message
Date: 2004-07-10 20:56:22
Message-ID: 20040710135622.A6381@cookie.varlena.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-07-10 21:02:25 Re: [BUGS] BUG #1118: Misleading Commit message
Previous Message Bruce Momjian 2004-07-10 20:45:00 Re: Nested Transactions, Abort All