Re: [feature] cached index to speed up specific queries on extremely large data sets

On Fri, Apr 11, 2014 at 2:12 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Apr 11, 2014 at 9:53 PM, lkcl . <luke(dot)leighton(at)gmail(dot)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.