Re: UPDATE has a bug to update tables with an index of 2

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Ian Barwick <barwick(at)gmx(dot)net>
Cc: Andreas Schmitz <andreas(dot)schmitz(at)as-dataservice(dot)de>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: UPDATE has a bug to update tables with an index of 2
Date: 2003-05-17 16:15:09
Message-ID: 20030517091355.S99020-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Sat, 17 May 2003, Ian Barwick wrote:

> On Friday 16 May 2003 21:46, Andreas Schmitz wrote:
>
> > Please enter a FULL description of your problem:
> > ------------------------------------------------
> >
> > Short: UPDATE has a bug to update tables with an index of 2 columns
> (...)
> > update test2 set v2=v2+2;
> > ERROR: Duplizierter Wert kann nicht in Unique-Index uq_test
> > eingefgt werden
>
> -> "Cannot insert a duplicate key into unique index uq_test"
>
> I would contend this is not a bug but a feature (or at most
> not-yet-implemented functionality, i.e. no ability to defer
> constraints other than foreign keys).

IIRC, it's a known bug. The constraint is checked at the wrong time, even
for non-deferred unique constraints the check is supposed to happen after
all the rows have been changed not as the rows are being changed.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Schmitz 2003-05-17 16:53:06 Re: UPDATE has a bug to update tables with an index of 2 columns
Previous Message Andreas Schmitz 2003-05-17 07:38:10 Re: UPDATE has a bug to update tables with an index of 2 columns