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 18:04:14 -0400
Message-ID: <8975.992901854@sss.pgh.pa.us> (raw)
In-Reply-To: <992901470.6585.2.camel@rivest.xdrive.com>
References: <992898628.6594.1.camel@rivest.xdrive.com>
<8896.992900535@sss.pgh.pa.us>
<992901470.6585.2.camel@rivest.xdrive.com>
Christopher Smith <x@xman.org> writes:
>> 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...
> Sorry, it is indeed a transcription error (sadly).
Oh well. The next thought, given that you mention threads, is that
you've got multiple threads issuing commands to the same backend
connection; in which case the interlocking you think you have doesn't
exist at all...
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: <8975.992901854@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