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

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(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-11 14:01:09
Message-ID: 40F14825.2080703@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 7/10/2004 10:54 AM, Bruce Momjian wrote:
> 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.
>

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(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-07-11 15:01:39 Re: [BUGS] BUG #1118: Misleading Commit message
Previous Message Bruce Momjian 2004-07-11 13:02:06 Re: Dump/Restore of cvs regression database gives invalid timestamp

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-11 15:01:39 Re: [BUGS] BUG #1118: Misleading Commit message
Previous Message Dennis Bjorklund 2004-07-11 05:40:17 Re: Nested Transactions, Abort All