Skip site navigation (1) Skip section navigation (2)

Re: BUG #2511: violation of primary key on update with 2

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: james <james(at)mercstudio(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2511: violation of primary key on update with 2
Date: 2006-07-03 20:21:48
Message-ID: 1151958108.2479.305.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: 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


In response to

pgsql-bugs by date

Next:From: Tomasz OstrowskiDate: 2006-07-03 20:31:07
Subject: query very slow when enable_seqscan=on
Previous:From: Phil FrostDate: 2006-07-03 18:19:09
Subject: BUG #2512: pg_dump produces unrestorable output when table and serial sequence are not in the same schema

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group