Change the default [tgenabled] for new "internal" triggers ? - Mailing list pgsql-general

From
Subject Change the default [tgenabled] for new "internal" triggers ?
Date
Msg-id F3CBFBA88397EA498B22A05FFA9EC49D697BB34F@MX22A.corp.emc.com
Whole thread Raw
Responses Re: Change the default [tgenabled] for new "internal" triggers ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Today I learned that . . .
the firing of even "internally generated constraint triggers" is affected by the value of [session_replication_role].

Sadly, I had previously assumed that such "internal" triggers did not care about [s_r_r].

Also learned that . . .
when a FK constraint gets made, its pg_trigger.tgenabled = ' O'.

QUESTION:
Is the a way to configure Postgres such that tgenabled = ' A' automatically when the FK constraint gets made ?

Or must I !un-automatedly! do a . . .
  alter table MYTABLE    ENABLE ALWAYS TRIGGER "RI_ConstraintTrigger_18656"
whenever
somebody makes a FK ?!?

Thanks,
-dvs-


pgsql-general by date:

Previous
From: Gerhard Wiesinger
Date:
Subject: Re: PostgreSQL 64 Bit XIDs - Transaction IDs
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 64 Bit XIDs - Transaction IDs