From: Jan Peters <petersjan@gmx.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Rollback locks table - why?
Date: Thu, 20 Mar 2008 16:17:58 +0100
Message-ID: <20080320151758.188000@gmx.net> (raw)
In-Reply-To: <9890.1206025894@sss.pgh.pa.us>
References: <20080320134208.42400@gmx.net>
<9890.1206025894@sss.pgh.pa.us>
Hello Tom,
> so the problem must be in something you didn't show us. What exactly
> are you doing to decide that you need to roll back? Also, none of these
> statements (except the CREATE) would take an exclusive lock on test, so
> there must be something else going on that you didn't show us.
That is exactly what confuses me. I just put the above code in the SQL Query Editor of my Admin App (e.g. PGAdmin III) and click the run button, nothing else. First time I get "duplicate unique key" second time "
ERROR: current transaction is aborted, commands ignored until end of transaction block"...
Regards
Jan
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf@gmx
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: petersjan@gmx.at, tgl@sss.pgh.pa.us
Subject: Re: Rollback locks table - why?
In-Reply-To: <20080320151758.188000@gmx.net>
* 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