Re: WIP: Triggers on VIEWs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIP: Triggers on VIEWs
Date
Msg-id 18215.1281981028@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP: Triggers on VIEWs  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: WIP: Triggers on VIEWs  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> On 15 August 2010 18:38, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>> There are still a number of things left todo:
>> �- extend ALTER VIEW with enable/disable trigger commands

> On further reflection, I wonder if the ability to disable VIEW
> triggers is needed/wanted at all.

AFAIK the only real use for disabling triggers is in connection with
trigger-based replication systems.  A view wouldn't be carrying
replication-related triggers anyway, so I think this could certainly
be left out of a first cut.

You aren't saying that you can see some reason why this couldn't be
added later, if wanted, correct?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Git migration timeline
Next
From: Tom Lane
Date:
Subject: Re: Todays git migration results