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

Поиск
Список
Период
Сортировка
Искать
От
Nis Jørgensen
Тема
Re: Why the ERROR: duplicate key violates unique constraint "master_pkey" is raised? - Is this a Bug?
Дата
Msg-id
fdih83$lkn$1@sea.gmane.org
Ответ на
Список
Дерево обсуждения
Re: Why the ERROR: duplicate key violates uniqueconstraint "master_pkey" is raised? - Is this a Bug? "Anoo Sivadasan Pillai" <aspillai@in.rm.com>
Re: Why the ERROR: duplicate key violates uniqueconstraint "master_pkey" is raised? - Is this a Bug? Reece Hart <reece@harts.net>
Re: Why the ERROR: duplicate key violates uniqueconstraint "master_pkey" is raised? - Is this a Bug? "Phoenix Kiula" <phoenix.kiula@gmail.com>
Re: Why the ERROR: duplicate key violates uniqueconstraint "master_pkey" is raised? - Is this a Bug? Richard Broersma Jr <rabroersma@yahoo.com>
Alban Hertroys skrev:
> 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.


I don't understand your query. I don't think you can use a correlated
subquery in that way.

Anyway, tricks like these might work. They might stop working without
warning, if the plan changes. Relying on unspecified behavior is a
recipe for trouble.

Nis

В списке pgsql-general по дате отправления
От: Tom Allison
Дата:
Сообщение: Re: Debian problem...
От: Stefan Schwarzer
Дата:
FAQ