Re: WIP: Triggers on VIEWs

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: Triggers on VIEWs
Date: 2010-08-16 18:35:57
Message-ID: AANLkTi=N8LOAWpFrt2nBm6Ci5owp+nM+DPNo9Z416x7Y@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16 August 2010 18:50, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
>> On 15 August 2010 18:38, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)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?
>

Yes. It should be easy to add later if wanted. I just don't see much
use for it, and I don't want to add more to an already quite big
patch, if it's not really needed.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-08-16 18:45:52 Re: Todays git migration results
Previous Message Kevin Grittner 2010-08-16 18:35:26 Re: Git migration timeline