From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Marcel Gsteiger" <Marcel(dot)Gsteiger(at)milprog(dot)ch> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems with unique restrictions |
Date: | 2007-01-13 16:22:32 |
Message-ID: | 24871.1168705352@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Marcel Gsteiger" <Marcel(dot)Gsteiger(at)milprog(dot)ch> writes:
> Now since I upgraded to 8.2 I have problems inserting data into tables that have unique indexes. Ugly enough, I get the message 'duplicate key violates unique constraint' when inserting the very first record into a table. This happens everytime when the new tuple references another tuple that has been inserted just before this one in the same transaction.
> Putting a "SET CONSTRAINTS ALL DEFERRED" in my procedure does not help.
> To me it looks that something with referential integrity checking goes wrong, but in this case the error message would be misleading.
RI would not have anything to do with a duplicate-key error.
Do you have any SERIAL-type columns in these tables? My first thought
is of a sequence that hasn't been updated to be above the existing ID
values. It's fairly easy to get into such a state if you do anything
but a plain vanilla dump-all-and-reload-all update process ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-13 16:31:07 | Re: FK Constraint on index not PK |
Previous Message | Tom Lane | 2007-01-13 16:19:53 | Re: FK Constraint on index not PK |