Re: Re: Why the ERROR: duplicate key violates unique constraint "master_pkey" is raised? - Is this a Bug?

From: Alban Hertroys <a(dot)hertroys(at)magproductions(dot)nl>
To: Nis Jørgensen <nis(at)superlativ(dot)dk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Why the ERROR: duplicate key violates unique constraint "master_pkey" is raised? - Is this a Bug?
Date: 2007-09-28 08:30:41
Message-ID: 46FCBBB1.1090503@magproductions.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Nis Jørgensen wrote:
> If you can't wait, you are probably better off working around the
> problem. Standard solution is to do:
>
> UPDATE master SET m2 = -m2;
> UPDATE master SET m2 = -m2+1;
>
> or something similar.

Would something like

UPDATE master set m2 = master2.m2
FROM (
SELECT m2 +1
FROM master m
WHERE m.master_id = master.master_id
ORDER BY m2 DESC
) master2

work? I think it might be faster (and possibly cause less index bloat)
than doing two consequent updates.

Haven't tested this though...

--
Alban Hertroys
alban(at)magproductions(dot)nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede

// Integrate Your World //

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nis Jørgensen 2007-09-28 08:36:52 Re: Normalized Tables & SELECT [was: Find "smallest common year"]
Previous Message olivier.scalbert@algosyn.com 2007-09-28 08:22:49 importing large files