Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) - Mailing list pgsql-patches

From Satoshi Nagayasu
Subject Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)
Date
Msg-id 42C4F137.6000507@nttdata.co.jp
Whole thread Raw
In response to Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-patches
> The table owner can drop and create triggers - so why shouldn't they be
> able to enable and disable them?

For convenience or easy operation.

I believe the user doesn't like to create same triggers again and again.

Christopher Kings-Lynne wrote:
>>>ALTER TABLE <table> ENABLE TRIGGER <trigname>
>>>ALTER TABLE <table> DISABLE TRIGGER <trigname>
>>
>>
>>Bruce said to allow them only super-user,
>>but currently this patch allows also the table owner.
>
>
> The table owner can drop and create triggers - so why shouldn't they be
> able to enable and disable them?
>
> Chris
>
>


--
NAGAYASU Satoshi <nagayasus@nttdata.co.jp>

pgsql-patches by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)