From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] REFRESH MATERIALIZED VIEW locklevel |
Date: | 2013-03-08 18:34:02 |
Message-ID: | 513A2F1A.3010408@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On 03/08/2013 10:09 AM, Merlin Moncure wrote:
>
> On Fri, Mar 8, 2013 at 11:59 AM, Josh Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-03-09 01:01:53 | Re: [pgsql-advocacy] Call for Google Summer of Code mentors, admins |
Previous Message | Merlin Moncure | 2013-03-08 18:09:23 | Re: REFRESH MATERIALIZED VIEW locklevel |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-03-08 19:21:58 | Re: Why do we still perform a check for pre-sorted input within qsort variants? |
Previous Message | Merlin Moncure | 2013-03-08 18:09:23 | Re: REFRESH MATERIALIZED VIEW locklevel |