Problems with unique restrictions

From: "Marcel Gsteiger" <Marcel(dot)Gsteiger(at)milprog(dot)ch>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Problems with unique restrictions
Date: 2007-01-13 08:33:46
Message-ID: s5a8a78c.006@milprog1.milprog.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all

I have a PL/PGSQL conversion procedure that reads a "source table" and then inserts tuples into several related tables. Recently I upgraded from 8.1 to 8.2.0, then to 8.2.1.

With 8.1 everything worked fine.

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.

Is there any known change/problem in this area? If not, I will try to strip down my procedure to something simple that documents my problems.

Regards
--Marcel

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shane Ambler 2007-01-13 08:34:40 Re: PostgreSQL Connections?
Previous Message Stéphane Schildknecht 2007-01-13 07:52:42 Re: FK Constraint on index not PK