RE: Primary Key Update issue ? - Mailing list pgsql-general

Hi Andreas,

Thanks a lot for your answer, which solves this case.

I was still a bit surprised as this is linked to transaction management while I have here a single statement until I saw the Compatibility Remark in documentation : Also, PostgreSQL checks non-deferrable uniqueness constraints immediately, not at end of statement as the standard would suggest.

Regards,

Patrick Fiche

From: Andreas Joseph Krogh <andreas@visena.com>
Sent: Friday, September 6, 2019 11:17 AM
To: pgsql-general@lists.postgresql.org
Subject: Sv: Primary Key Update issue ?

Hello,

 

While doing some testing on a Postgresql database, I encountered a strange behavior which is very simple to reproduce.

I just wanted to know if this is expected behavior or if it should be considered as an issue.

 

The scenario to reproduce it is the following.

 

CREATE TABLE Test ( pKey integer, Val integer, CONSTRAINT PK_Test PRIMARY Key( pKey ) );

 

INSERT INTO Test( pKey, Val ) VALUES ( 1, 1 );

INSERT INTO Test( pKey, Val ) VALUES ( 2, 2 );

 

UPDATE Test SET pKey = pKey + 1;

 

Here is the error that I get.

 

SQL Error [23505]: ERROR: duplicate key value violates unique constraint "pk_test"

  Detail: Key (pkey)=(2) already exists.

 

I was expecting pKey to be incremented for each row, which would still respect the unique constraint….

 

I’m currently using PostgreSQL 11.5 but have the same problem on PostgreSQL 10.3 server.

 

Best Regards,