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

From Jan Wieck
Subject Re: [BUGS] BUG #1118: Misleading Commit message
Date
Msg-id 40F14825.2080703@Yahoo.com
Whole thread Raw
In response to Re: [BUGS] BUG #1118: Misleading Commit message  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [BUGS] BUG #1118: Misleading Commit message  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 7/10/2004 10:54 AM, Bruce Momjian wrote:
> 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.
> 

Either changing the command tag or let COMMIT of an aborted transaction 
fail (and stay in aborted transaction state). Those are the only two 
clean ways to communicate to the client "no, I cannot commit".


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Nested Transactions, Abort All
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #1118: Misleading Commit message