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

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

elein wrote:
> 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.

If it is a problem, hopefully we will hear about it during beta. I will
mention is as a backward-compatibility issue in the release notes.

---------------------------------------------------------------------------

>
> 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
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-07-10 21:06:51 Re: Point in Time Recovery
Previous Message elein 2004-07-10 20:56:22 Re: [BUGS] BUG #1118: Misleading Commit message