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

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

Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> 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".

Well, the latter would *certainly* create compatibility problems, so
I don't find it preferable ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2004-07-11 19:14:38 Re: Dump/Restore of cvs regression database gives invalid timestamp syntax error
Previous Message Jan Wieck 2004-07-11 14:01:09 Re: [BUGS] BUG #1118: Misleading Commit message

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-11 15:17:19 Re: plperl (7.5)
Previous Message Jan Wieck 2004-07-11 14:01:09 Re: [BUGS] BUG #1118: Misleading Commit message