Re: Materialized views WIP patch - Mailing list pgsql-hackers

From David Johnston
Subject Re: Materialized views WIP patch
Date
Msg-id 68BBE549-5AB1-4776-BC8F-4ED301C0227B@yahoo.com
Whole thread Raw
In response to Re: Materialized views WIP patch  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Nov 27, 2012, at 5:25, Dimitri Fontaine <dimitri@2ndQuadrant.fr> wrote:

>
> So my proposal for the current feature would be:
>
>  ALTER MATERIALIZED VIEW mv UPDATE [ CONCURRENTLY ];
>  UPDATE MATERIALIZED VIEW mv;
>
> The choice of keywords and syntax here hopefully clearly hint the user
> about the locking behavior of the commands, too. And as we said, the
> bare minimum for this patch does *not* include the CONCURRENTLY option,
> which we still all want to have (someday). :)
>

I dislike using ALTER syntax to perform a data-only action.

The other advantage of non-functional syntax is that you could more easily supply some form of where clause should you
onlywant to perform a partial refresh.  With a function call that becomes more obtuse. 

David J.


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: DEALLOCATE IF EXISTS
Next
From: Dimitri Fontaine
Date:
Subject: Re: Materialized views WIP patch