Re: Watching for view changes

From: Mitar <mmitar(at)gmail(dot)com>
To: George Neuner <gneuner2(at)comcast(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Watching for view changes
Date: 2018-12-24 07:06:51
Message-ID: CAKLmikN=J+96wDX_PX1CGnKo9gK5=jVpR+Tbn06dd5gcnC3fqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

On Fri, Dec 21, 2018 at 11:10 PM George Neuner <gneuner2(at)comcast(dot)net> wrote:
> A materialized view IS exactly such a deliberate cache of results from
> applying a view. It is a real table that can be monitored for changes
> using INSERT, UPDATE and/or DELETE triggers.

Are you sure one can use triggers on a materialized view? I am getting:

"my_materialized_view" is not a table or view

as an error when I am trying to create a trigger on materialized view.

Mitar

--
http://mitar.tnode.com/
https://twitter.com/mitar_m

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message George Neuner 2018-12-24 07:59:16 Re: Watching for view changes
Previous Message Mitar 2018-12-24 04:21:22 Determine in a trigger if UPDATE query really changed anything