From: Christopher Smith <x@xman.org>
To: pgsql-sql@postgresql.org
To: pgsql-jdbc@postgresql.org
Subject: Problems ensuring uniqueness?
Date: 18 Jun 2001 14:10:27 -0700
Message-ID: <992898628.6594.1.camel@rivest.xdrive.com> (raw)
Hi there. I'm currently using Postgresql 7.0.3, accessing using the JDBC
drivers. I'm enforcing the most severe transaction isolation available
(serializable). I'm currently doing something like the following (this
is pseudo code, with the if being performed in Java):
begin
lock table foo in access exclusive mode
select count(*) from foo where key1 = bar, key2 = baz
if count > 1
rollback
else
insert into foo (key1, key2, other) values (bar, baz, stuff)
commit
Now, table foo has a primary key made up of key1 & key2. Without
concurrent access, the code works great. However, provided I use enough
threads, I inevitably get back errors from the database indicating that
I've tried to insert a record which violates the uniquness of the
primary key.
Is there away to avoid this error by doing my SQL & locking properly, or
should I just catch the exception and deal with it?
--Chris
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: x@xman.org, pgsql-jdbc@postgresql.org
Subject: Re: Problems ensuring uniqueness?
In-Reply-To: <992898628.6594.1.camel@rivest.xdrive.com>
* 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