Re: ALTER TRIGGER DISABLE/ENABLE

From: Tino Wildenhain <tino(at)wildenhain(dot)de>
To: 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 10:37:43
Message-ID: 316748750.1038310663@liza
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

--On Dienstag, 26. November 2002 09:43 +0100 Christoph Dalitz
<christoph(dot)dalitz(at)hs-niederrhein(dot)de> 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?

Sounds reasonable, but should a form ALTER TABLE DISABLE|ENABLE [ALL]
TRIGGER
or something like that be available too?
This could be done for RI-Triggers on a table while restoring data.

Regards
Tino

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tino Wildenhain 2002-11-26 10:52:37 Re: COPY COMMAND
Previous Message Savita 2002-11-26 10:32:09 Re: COPY COMMAND