Change FK trigger creation order to better support self-referential FKs.

When a foreign-key constraint references another column of the same table,
row updates will queue both the PK's ON UPDATE action and the FK's CHECK
action in the same event.  The ON UPDATE action must execute first, else
the CHECK will check a non-final state of the row and possibly throw an
inappropriate error, as seen in bug #6268 from Roman Lytovchenko.

Now, the firing order of multiple triggers for the same event is determined
by the sort order of their pg_trigger.tgnames, and the auto-generated names
we use for FK triggers are "RI_ConstraintTrigger_NNNN" where NNNN is the
trigger OID.  So most of the time the firing order is the same as creation
order, and so rearranging the creation order fixes it.

This patch will fail to fix the problem if the OID counter wraps around or
adds a decimal digit (eg, from 99999 to 100000) while we are creating the
triggers for an FK constraint.  Given the small odds of that, and the low
usage of self-referential FKs, we'll live with that solution in the back
branches.  A better fix is to change the auto-generated names for FK
triggers, but it seems unwise to do that in stable branches because there
may be client code that depends on the naming convention.  We'll fix it
that way in HEAD in a separate patch.

Back-patch to all supported branches, since this bug has existed for a long
time.

diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
index 4e3e04d077bb485b92bf6364df5fefed91ced765..390abe6f1f358330e0aa94f39e695b816cd958c5 100644 (file)
--- a/src/backend/commands/tablecmds.c
+++ b/src/backend/commands/tablecmds.c
@@ -4617,13 +4617,6 @@ createForeignKeyTriggers(Relation rel, FkConstraint *fkconstraint,
        /* Make changes-so-far visible */
        CommandCounterIncrement();
 
-       /*
-        * Build and execute a CREATE CONSTRAINT TRIGGER statement for the CHECK
-        * action for both INSERTs and UPDATEs on the referencing table.
-        */
-       CreateFKCheckTrigger(myRel, fkconstraint, constraintOid, true);
-       CreateFKCheckTrigger(myRel, fkconstraint, constraintOid, false);
-
        /*
         * Build and execute a CREATE CONSTRAINT TRIGGER statement for the ON
         * DELETE action on the referenced table.
@@ -4725,6 +4718,27 @@ createForeignKeyTriggers(Relation rel, FkConstraint *fkconstraint,
        fk_trigger->args = NIL;
 
        (void) CreateTrigger(fk_trigger, constraintOid);
+
+       /* Make changes-so-far visible */
+       CommandCounterIncrement();
+
+       /*
+        * Build and execute CREATE CONSTRAINT TRIGGER statements for the CHECK
+        * action for both INSERTs and UPDATEs on the referencing table.
+        *
+        * Note: for a self-referential FK (referencing and referenced tables are
+        * the same), it is important that the ON UPDATE action fires before the
+        * CHECK action, since both triggers will fire on the same row during an
+        * UPDATE event; otherwise the CHECK trigger will be checking a non-final
+        * state of the row.  Because triggers fire in name order, we are
+        * effectively relying on the OIDs of the triggers to sort correctly as
+        * text.  This will work except when the OID counter wraps around or adds
+        * a digit, eg "99999" sorts after "100000".  That is infrequent enough,
+        * and the use of self-referential FKs is rare enough, that we live with
+        * it for now.  There will be a real fix in PG 9.2.
+        */
+       CreateFKCheckTrigger(myRel, fkconstraint, constraintOid, true);
+       CreateFKCheckTrigger(myRel, fkconstraint, constraintOid, false);
 }
 
 /*

diff --git a/src/test/regress/expected/foreign_key.out b/src/test/regress/expected/foreign_key.out
index e24ceb51a87f480507abb2328cb983c5727107f2..fb3061e19a1f1e7a7533752612a607a04e588180 100644 (file)
--- a/src/test/regress/expected/foreign_key.out
+++ b/src/test/regress/expected/foreign_key.out
@@ -1297,3 +1297,35 @@ SELECT * FROM tasks;
 (3 rows)
 
 COMMIT;
+--
+-- Test self-referential FK with CASCADE (bug #6268)
+--
+create temp table selfref (
+    a int primary key,
+    b int,
+    foreign key (b) references selfref (a)
+        on update cascade on delete cascade
+);
+NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "selfref_pkey" for table "selfref"
+insert into selfref (a, b)
+values
+    (0, 0),
+    (1, 1);
+begin;
+    update selfref set a = 123 where a = 0;
+    select a, b from selfref;
+  a  |  b  
+-----+-----
+   1 |   1
+ 123 | 123
+(2 rows)
+
+    update selfref set a = 456 where a = 123;
+    select a, b from selfref;
+  a  |  b  
+-----+-----
+   1 |   1
+ 456 | 456
+(2 rows)
+
+commit;

diff --git a/src/test/regress/sql/foreign_key.sql b/src/test/regress/sql/foreign_key.sql
index 519a5056af04906e37eec9ea69c6faeff9241452..5ae8b88cd3d28a36c3e7ea949018525d64149572 100644 (file)
--- a/src/test/regress/sql/foreign_key.sql
+++ b/src/test/regress/sql/foreign_key.sql
@@ -921,3 +921,25 @@ SELECT * FROM tasks;
 DELETE FROM users WHERE id = 2;
 SELECT * FROM tasks;
 COMMIT;
+
+--
+-- Test self-referential FK with CASCADE (bug #6268)
+--
+create temp table selfref (
+    a int primary key,
+    b int,
+    foreign key (b) references selfref (a)
+        on update cascade on delete cascade
+);
+
+insert into selfref (a, b)
+values
+    (0, 0),
+    (1, 1);
+
+begin;
+    update selfref set a = 123 where a = 0;
+    select a, b from selfref;
+    update selfref set a = 456 where a = 123;
+    select a, b from selfref;
+commit;