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

From Bruce Momjian
Subject Re: [BUGS] BUG #1118: Misleading Commit message
Date
Msg-id 200407101737.i6AHbxS26698@candle.pha.pa.us
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
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Memory management with C aggregate
Next
From: Robert Treat
Date:
Subject: Re: Update pg_tables, pg_index views to show tablespace name?