Re: Problem with aborting entire transactions on error - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: Problem with aborting entire transactions on error
Date
Msg-id ka511t$7bu$1@ger.gmane.org
Whole thread Raw
In response to Re: Problem with aborting entire transactions on error  (Chris Angelico <rosuav@gmail.com>)
Responses Re: Problem with aborting entire transactions on error  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
Chris Angelico, 10.12.2012 16:47:
> The other part of the problem is that you're using transactions for
> something other than transactional integrity. You're batching up
> transactions in order to improve performance. That's certainly
> possible, but you're using the database "oddly", so you can't expect
> it to behave according to your modified set of rules. That's why the
> transaction functions like a transaction, not like a commit-point.


Just as a side-note: Oracle also allows you to commit a "transaction" even if some of the statements failed
e.g. the commit of 20 inserts would only "commit" the ones that were successful.

Regards
Thomas


pgsql-general by date:

Previous
From: "David Johnston"
Date:
Subject: Re: Problem with aborting entire transactions on error
Next
From: Tom Lane
Date:
Subject: Re: Out of memory error