On Thu, 18 Jan 2001, Kovacs Zoltan Sandor wrote:
> I realized that an error will abort a transaction all the time.
> Unfortunately I usually send millions of rows of INSERTs in a transaction
> and if there is some error in the middle of the code I got the message
> if I try to INSERT a new row:
>
> NOTICE: current transaction is aborted, queries ignored until end of
> transaction block
> *ABORT STATE*
>
> OK, this is a nice feature. But I sometimes make mistakes at the end of
> the transaction and I got no such message. There is no easy way to find
> out if there was an aborted transaction or not. Can I consider this as a
> bug? Probably not, but I suggest dropping something similar immediately
> after aborting. Your opinion, please? :-)
Well, you should have gotten an error message from the statement that was
in error in any case, but maybe a message on the commit/end that says
that the transaction was aborted due to errors would be nice.
