Re: New parameter RollbackError to control rollback behavior on error
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2014-03-31T12:40:56Z
Lists: pgsql-hackers
Attachments
- 20140331_error_rollback_v2.patch (text/plain) patch v2
On Wed, Mar 26, 2014 at 5:53 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > * I'm not too fond of the RollbackError name. It sounds like "an error while > rolling back". I googled around and found out that DataDirect's proprietary > driver has the same option, and they call it TransactionErrorBehavior. See > http://blogs.datadirect.com/2013/07/solution-unexpected-postgres-current-transaction-aborted-error.html. > > * Instead of using 0-2 as the values, let's give them descriptive names. > Something like "none", "RollbackTransaction", "RollbackStatement". > (actually, we'll probably want to also allow the integers, to keep the > connection string short, as there is a size limit on that) OK, I have been working more on that, giving the attached patch. The parameter name is changed to TransactionErrorBehavior, able to use the values "Statement", "Nop", "Transaction" and "Default". "Default" corresponds to the default behavior, that is used to set the rollback behavior depending on the Postgres version driver is connected with. As of now, TransactionErrorBehavior does not accept integer values as it makes the patch a bit more simple, this could be added with some atoi calls in dlg_specific.c. I have updated dlg_wingui.c as well. Patch has always its set of docs and regression tests. Regards, -- Michael