unique constraint when updating tables - Mailing list pgsql-general

From gao iqiang
Subject unique constraint when updating tables
Date
Msg-id 5323452d0608211739l6ff0145btfc1a052b3073f207@mail.gmail.com
Whole thread Raw
Responses Re: unique constraint when updating tables
Re: unique constraint when updating tables
List pgsql-general

Hello,
    I met the following problem when i am using PostgreSQL as a backend database:
    I have a table "tabrel(a int primary key, b int)", and now there are for example 100 records with column 'a' be from 1 to 100. When i'm going to add one to each 'a' and intended to get 'a' varing from 2 to 101, i use SQL query as "update tabrel set a=a+1" , but i got " ERROR: duplicate key violates unique constraint tabrel_a_key".
    In my experience with using Oracle, SQL Server and Mysql, such SQL should be executed succussfully. After i met this problem, i turned back to some textbook about database transaction and i got information like this "it is ok to have some inconsistent state during one transaction, only if it is consistent after the transaction is finished succesfully." 
    And now, i'm wondering what's the problem with this SQL query? How 'update' is executed in the backend?
   
    I'm using PostgreSQL 8.1.4.

    Thanks
    Shawn Gao                                   
    2006-08-22

pgsql-general by date:

Previous
From: "Arturo Perez"
Date:
Subject: [8.1.4] Create index on timestamp fails
Next
From: "macgillivary"
Date:
Subject: Re: Massive slowdown when LIMIT applied