Osahon Oduware <[email protected]> writes: > The pg_trigger_depth() function solved the issue. Thanks a lot, you made my > day.
If you start finding that that gets in your way for other purposes, you
might try making table A's trigger function be SECURITY DEFINER and
owned by a role that has permissions to change table B.
regards, tom lane
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
