From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cannot set view triggers to replica |
Date: | 2015-05-30 08:10:23 |
Message-ID: | CAB7nPqT_rkQadNRTbD2uPo_JX2S-GShFUzbnwGNAM8hvgSrKRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 30, 2015 at 11:47 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> It appears to be an omission that ALTER TABLE ... ENABLE TRIGGER and
> similar commands don't allow acting on views, even though we now have
> triggers on views.
True, now isn't it something that should be as well part of ALTER VIEW?
> Similarly, the ALTER TABLE ... ENABLE RULE commands only allow acting on
> tables, even though rules can also exist on views and materialized views.
I think that ALTER VIEW and ALTER MATERIALIZED VIEW should be able to
accept the command as well.
> Attached is a sample patch. It appears we don't have any regression
> tests for this.
This sounds like a mandatory condition for this patch.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-05-30 08:19:50 | Re: initdb -S versus superuser check and Windows restricted mode |
Previous Message | Peter Geoghegan | 2015-05-30 08:07:14 | Re: Free indexed_tlist memory explicitly within set_plan_refs() |