Jan Peters wrote:
> If I run the transaction block from above again I get first a unique key violation (that is ok, because that's what I trying to check for) but there is NO rollback to sp1, only the "Unique Key" error message and after that I get the dreaded "current transaction is aborted" error message and the system reports an EXCLUSIVE LOCK on the table (<IDLE>in transaction).
Am I correct in saying that your issue is really that you want an error
to trigger an automatic rollback to the last savepoint, but it does not
do so ?
If you issue the ROLLBACK manually (after you get the constraint error
or a "current transaction is aborted" message) does it work as you would
In response to
pgsql-sql by date
|Next:||From: Jan Peters||Date: 2008-03-20 14:30:05|
|Subject: Re: Rollback locks table - why?|
|Previous:||From: Craig Ringer||Date: 2008-03-20 13:44:34|
|Subject: Re: Select into|