Re: DEFERABLE vs. NOT DEFERABLE constraints - Mailing list pgsql-novice

From Tom Lane
Subject Re: DEFERABLE vs. NOT DEFERABLE constraints
Date
Msg-id 15200.1185306420@sss.pgh.pa.us
Whole thread Raw
In response to Re: DEFERABLE vs. NOT DEFERABLE constraints  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-novice
Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> On Tue, 24 Jul 2007, Claude Chaloux wrote:
>> Basically, the function inserts a row in a table (in the database I'm
>> testing with) that has a reference (foreign key set) to another table.
>> Under 7.4, I have no problem inserting the rows in the two tables even
>> when inserting in the table which column is being referenced first. On
>> 8.2 however, I get an error message "constraint violation".

> In 7.4, a not deferred trigger caused by a statement in a function was
> still delayed until the end of the statement that called the function. As
> of 8.0, a not deferred trigger is called at the end of the statement in
> the function.

Note that if the constraint is marked DEFERRABLE INITIALLY DEFERRED,
it should be checked at transaction end in either version.  Are you
sure you really have it set to deferred?

            regards, tom lane

pgsql-novice by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: DEFERABLE vs. NOT DEFERABLE constraints
Next
From: "Jill"
Date:
Subject: check (constraint) on point data type?