Re: REFRESH MATERIALIZED VIEW locklevel

On 03/08/2013 10:09 AM, Merlin Moncure wrote:
>
> On Fri, Mar 8, 2013 at 11:59 AM, Josh Berkus <josh@agliodbs.com> wrote:
>> Andres,

>> Further, we get pretty much one and only one chance to promote a new
>> major feature, which is when that feature is first introduced.
>> Improving the feature in the next version of Postgres is not news, so we
>> can't successfully promote it.  If we soft-pedal MVs in the 9.3
>> announcement, we will not be able to get people excited about them in
>> 9.4; they will be "yesterday's news".
>
> +1 on this.  they are useful to me as immediately and I work in busy
> environments.  the formal matview feature is a drop in replace for my
> ad hoc implementation of 'drop cache table, replace from view'.  I
> already have to work around the locking issue anyways -- sure, it
> would be great if I didn't have to do that either but I'll take the
> huge syntactical convenience alone.

Just to throw my +1 into the ring. Well written Josh.

JD


>
> merlin
>
>


--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579