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

From Zbigniew
Subject Re: Problem with aborting entire transactions on error
Date
Msg-id CALT7RM_KHj-p4sZkLs=4pPmiz-YJTjz8xNej3wBbeXYydtw8vA@mail.gmail.com
Whole thread Raw
In response to Re: Problem with aborting entire transactions on error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with aborting entire transactions on error  (David Johnston <polobo@yahoo.com>)
List pgsql-general
2012/12/11, Tom Lane <tgl@sss.pgh.pa.us>:

> The complexity and performance costs that people have mentioned are other
> good reasons not to change it; but even if the change were free on the
> server side, history says it's not something we ought to mess with.

Again: my suggestion was to add an option... with default value "keep
present functionality".
--
regards,
Zbigniew


pgsql-general by date:

Previous
From: Zbigniew
Date:
Subject: Re: Problem with aborting entire transactions on error
Next
From: Chris Angelico
Date:
Subject: Re: large database