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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 17:37:59
Message-ID: 200407101737.i6AHbxS26698@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >>> Do we want to add this to TODO:
> >>> * Issue an extra message when COMMIT completes a failed transaction
> >>
> >> No --- it's (a) wordy and (b) not responsive to the original complaint,
> >> which was that a client that examines command completion tags will be
> >> easily misled. We should either change the command tags or do nothing.
>
> > I am not excited about changing the command tag.
>
> I was not either to start with, but the more I think about it, the more
> I think it would be a good idea.

What tag would we use? ABORT?

--
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-bugs by date

  From Date Subject
Next Message Tom Lane 2004-07-10 18:44:11 Re: BUG #1188: evaluation order of select seems to be wrong
Previous Message Tom Lane 2004-07-10 16:48:14 Re: [BUGS] BUG #1118: Misleading Commit message

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2004-07-10 17:45:20 Re: Update pg_tables, pg_index views to show tablespace name?
Previous Message Tom Lane 2004-07-10 17:00:22 Re: Memory management with C aggregate