From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Smith <x@xman.org>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-jdbc@postgresql.org
Subject: Re: [SQL] Problems ensuring uniqueness?
Date: Mon, 18 Jun 2001 17:42:15 -0400
Message-ID: <8896.992900535@sss.pgh.pa.us> (raw)
In-Reply-To: <992898628.6594.1.camel@rivest.xdrive.com>
References: <992898628.6594.1.camel@rivest.xdrive.com>
Christopher Smith <x@xman.org> writes:
> 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.
Um ... surely that should be "if count > 0" ? Or was that just a
transcription error?
This approach certainly ought to work as desired given the exclusive
lock, so a silly typo seems like a plausible explanation...
regards, tom lane
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: tgl@sss.pgh.pa.us, x@xman.org, pgsql-jdbc@postgresql.org
Subject: Re: [SQL] Problems ensuring uniqueness?
In-Reply-To: <8896.992900535@sss.pgh.pa.us>
* 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