X-Original-To: pgsql-sql@postgresql.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by postgresql.org (Postfix) with SMTP id 30B0A474E42 for ; Sat, 8 Mar 2003 16:48:46 -0500 (EST) Received: (qmail 10018 invoked by uid 0); 8 Mar 2003 21:48:47 -0000 Date: Sat, 8 Mar 2003 22:48:46 +0100 (MET) From: daniel alvarez To: Rod Taylor Cc: pgsql-sql@postgresql.org MIME-Version: 1.0 References: <1047159202.28251.196.camel@jester> Subject: Re: Atomicity of UPDATE, interchanging values in unique column X-Priority: 3 (Normal) X-Authenticated-Sender: #0002681999@gmx.net X-Authenticated-IP: [217.185.184.254] Message-ID: <21780.1047160126@www48.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200303/213 X-Sequence-Number: 12253 > The first is what you want. PostgreSQL needs some work in the > evaluation of unique indexes to properly support it. > > Namely, when it sees a conflict when inserting into the index, it needs > to record the fact, and revisit the conflict at the end of the command. > Lots of work... OK. The long-term goal would then be to get rid of such oddities. But what can I do right now as a user to solve that issue for my application? There must be a better solution than the additional dummy update. Any ideas? Daniel Alvarez Arribas -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!