Re: ALTER TRIGGER DISABLE/ENABLE - Mailing list pgsql-general

From Jean-Luc Lachance
Subject Re: ALTER TRIGGER DISABLE/ENABLE
Date
Msg-id 3DE3CE7B.614EE99E@nsd.ca
Whole thread Raw
In response to Re: ALTER TRIGGER DISABLE/ENABLE  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: ALTER TRIGGER DISABLE/ENABLE  (Christoph Dalitz <christoph.dalitz@hs-niederrhein.de>)
List pgsql-general
I think thte sintax should be:

ALTER TABLE DISABLE|ENABLE TRIGGER {trigger name}|ALL



Bruce Momjian wrote:
>
> Christoph Dalitz wrote:
> > Hello,
> >
> > while there have been suggested some hacks on the system catalog
> > for disabling/enabling triggers, these have two serious disadvantages:
> >
> >  - they cannot be done by the owner of the trigger
> >    (only the DBA has write access to the system catalog)
> >  - messing in the system catalog for simple DB schema changes makes
> >    most users feel uneasy
> >
> > Oracle has an SQL command "ALTER TRIGGER triggername DISABLE|ENABLE".
> > Were it possible to put this command on the TODO list for a future PG release?
>
> Already on TODO list:
>
>         * Allow triggers to be disabled [trigger]
>
> I will add your email to the TODO.detail thread.
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

pgsql-general by date:

Previous
From: "Bjoern Metzdorf"
Date:
Subject: Re: Updating table with max from another table
Next
From: Diogo Biazus
Date:
Subject: Re: postgres taking longer to update