FK constraint enforcement may be deferred, but only to the end of the DML
transaction. Can someone provide an example where a SELECT statement that
is not in that DML transaction and that can view only committed data can see
a FK-side row that doesn't join with any PK-side row?
I don't think I understand why the volatile function scenario. Can a
volatile function somehow circumvent FK enforcement? If not, then why is
the volatile function scenario different than any other DML with respect to
the enforcement of FK constraints?
thank you,
/Jim F
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
