-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks, Tom.
This doesn't quite answer the case in which, say, an UPDATE is performed
and the underlying table has a .
OK, a piece of the puzzle is in place- all CHECKs are performed before
all TRIGGERs. But what is the actual order of constraint enf
Demian Lessa <[EMAIL PROTECTED]> writes:
> What I'm trying to figure out is how postgre identifies the *exact* set
> of constraints to enforce for each of the different commands above, and
> the order in which these are performed (since some checks are way more
> expensive than others).
Triggers o
