Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> My question is: When tgenabled is set to "D", how does that setting interact
> with session_replication_role and, is there a way to use tgenabled with a
> setting of "D" to prevent a particular trigger from firing. Using ALTER TABLE
> to disable the trigger won't work because the whole table is locked during
> the transaction and I only want the disabled trigger to apply to the current
> transaction in the current session.
I'll bet you're missing a relcache flush operation. I don't think an
update on pg_trigger will cause that by itself.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
