From: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: ALTER TRIGGER DISABLE/ENABLE |
Date: | 2002-11-26 19:41:47 |
Message-ID: | 3DE3CE7B.614EE99E@nsd.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Diogo Biazus | 2002-11-26 19:57:09 | Re: postgres taking longer to update |
Previous Message | Bjoern Metzdorf | 2002-11-26 19:41:45 | Re: Updating table with max from another table |