Re: BUG #2511: violation of primary key on update with 2 - Mailing list pgsql-bugs

From Simon Riggs
Subject Re: BUG #2511: violation of primary key on update with 2
Date
Msg-id 1151958108.2479.305.camel@localhost.localdomain
Whole thread Raw
In response to BUG #2511: violation of primary key on update with 2 tables  ("james" <james@mercstudio.com>)
List pgsql-bugs
On Mon, 2006-07-03 at 11:14 +0000, james wrote:

> i think it's a bug in postgresql ...

Primary Key constraints are not deferrable currently. This is a known
situation so this isn't a bug.

I would advise you not to update the PK of your tables. That usually
represents a modelling problem and so I'm not sure if people will spend
time on trying to make that work.

Use an indirect key or some other mechanism, such as Inserting into
another table and renaming them.

--
  Simon Riggs
  EnterpriseDB          http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "Nestor Ramirez (Speedy)"
Date:
Subject: Re: BUG #2507: Problem using two-phase commit
Next
From: Tomasz Ostrowski
Date:
Subject: query very slow when enable_seqscan=on