On Thu, Mar 31, 2016 at 9:30 AM, Matthew Syphus <msyp...@lhtac.org> wrote:
> I would like a trigger on a materialized view. Is this possible? I have > tried both an INSTEAD OF and BEFORE trigger with no luck. It responds > with: > > "project_milestone_mv" is not a table or view. > > It is absolutely present and spelled correctly. It is the same with or > without the schema qualification. Actual statement: > > > > CREATE TRIGGER project_milestone_upsert_trigger INSTEAD OF UPDATE > > ON tracking.project_milestone_mv FOR EACH ROW > > EXECUTE PROCEDURE tracking.project_milestone_upsert(); > > > > The documentation at > http://www.postgresql.org/docs/current/static/sql-createtrigger.html does > not explicitly exclude nor include materialized views. The most pertinent > part I’ve found simply states “The trigger will be associated with the > specified table, view, or foreign table” and later in reference to > table_name, “The name (optionally schema-qualified) of the table, view, > or foreign table the trigger is for.” I’ve found no mailing list entry > addressing triggers and whether “view” does not include _*materialized*_ > view. > > Does this indicate, then, that materialized views cannot have triggers? > > > > Postgres 9.5.1 > > CentOS 6.5 > > > That would seem to be sufficient evidence that indeed "materialized views" are not the same as "views" (or "tables") and that they have not been given the ability to be assigned triggers. While still implicit the documentation page for "SQL Commands" has separate entries for "CREATE VIEW" and "CREATE MATERIALIZED VIEW" which further supports them being distinct as opposed to materialized views being a specialization of view. David J.
