> -----Original Message----- > From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin- > owner@xxxxxxxxxxxxxx] On Behalf Of Kasia Tuszynska > Sent: Tuesday, November 29, 2011 3:35 PM > To: Kevin Grittner; pgsql-admin@xxxxxxxxxxxxxx > Subject: Re: transaction error handling > > Hi Kevin, > Thank you, that is very helpful. > I am not worried about the implicit commits. The "no implicit > savepoint" was more of an issue, since it created a necessity to create > and destroy savepoints per each sql statement to capture any statement > level error without losing a transaction, that approach has prohibitive > performance repercussions. > I will check out the ON_ERROR_ROLLBACK feature. > Thank you, > Sincerely, > Kasia Be aware that this option is a psql option and not one in the database itself, which means unless you are executing your SQL via psql it will not be of help to you. Also the implementation of this is that psql issues implicit savepoints for you before each command in a transaction and handles the rollback for you if needed (which sounds an awful lot like the performance concern you have). This is a major pain for porting Oracle based applications over for those that rely on this functionality. Brad. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
