From: Craig Ringer <craig@postnewspapers.com.au>
To: Jan Peters <petersjan@gmx.at>
Cc: pgsql-sql@postgresql.org
Subject: Re: Rollback locks table - why?
Date: Thu, 20 Mar 2008 22:57:15 +0900
Message-ID: <47E26D3B.4010102@postnewspapers.com.au> (raw)
In-Reply-To: <20080320134208.42400@gmx.net>
References: <20080320134208.42400@gmx.net>
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
expect?
--
Craig Ringer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: craig@postnewspapers.com.au, petersjan@gmx.at
Subject: Re: Rollback locks table - why?
In-Reply-To: <47E26D3B.4010102@postnewspapers.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox