David Greco <David_Greco@xxxxxxxxxxxxxxx> writes: > Since the trigger is defined as AFTER ROW, versus AFTER STATEMENT, I believe the trigger should be considered part of the statement, therefore the constraint should not be checked until after the row triggers have run. Any thoughts? Not sure that this is terribly well documented, but you can arrange for your triggers to fire before the FK-enforcement triggers. Triggers on the same table and event type fire in alphabetical (in ASCII) order, so just choose a name that's before the FK triggers, which if memory serves have names starting with "RI_". So for instance CREATE TRIGGER "Parent_ar_trg" ... would have worked the way you want. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
