Re: [feature] cached index to speed up specific queries on extremely large data sets - Mailing list pgsql-hackers

From lkcl .
Subject Re: [feature] cached index to speed up specific queries on extremely large data sets
Date
Msg-id CAPweEDxQF7PQBsiGxzzdTOrT6=6XExqvZR7xKgBYhB1-COiorg@mail.gmail.com
Whole thread Raw
In response to Re: [feature] cached index to speed up specific queries on extremely large data sets  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Fri, Apr 11, 2014 at 2:12 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Fri, Apr 11, 2014 at 9:53 PM, lkcl . <luke.leighton@gmail.com> wrote:
>>> section: https://wiki.postgresql.org/wiki/Materialized_Views.
> When updating a materialized view, or refreshing it, you need as well
> to be aware that an exclusive lock is taken on it during the refresh
> in 9.3, so the materialized view cannot be accessed for read queries.
ok.  as long as the storage of data (in the underlying table) is not
adversely affected, that would be fine.  as this is the hackers list
and this turns out to be more a user question i'll leave it for now.

>>  awesome.  uhhh, well that was easy *lol*.  once i am paid, whom do i
>> send the payment to for the fast response and incredibly valuable
>> information? :)  [this is a serious question!]
> This can be helpful:
> http://www.postgresql.org/about/donate/
thank you michael.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [feature] cached index to speed up specific queries on extremely large data sets
Next
From: Tom Lane
Date:
Subject: Re: WIP patch (v2) for updatable security barrier views