From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Kovacs Zoltan Sandor <tip(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: notice on transaction abort? |
Date: | 2001-01-18 21:56:48 |
Message-ID: | Pine.BSF.4.21.0101181353290.1647-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Kaare Rasmussen | 2001-01-18 21:58:37 | Re: PostgreSQL HOWTO |
Previous Message | Tom Lane | 2001-01-18 21:46:10 | Re: Re: ltsWriteBlock: failed to write block XX of temporary file. Perharps out of disk space... |