"k...@rice.edu" <k...@rice.edu> wrote: > The question I have, which applies to the matview support as > well, is "How can we transparently substitute usage of the > in-memory columnar store/matview in a SQL query?".
My take on that regarding matviews is: (1) It makes no sense to start work on this without a far more sophisticated concept of matview "freshness" (or "staleness", as some products prefer to call it). (2) Work on query rewrite to use sufficiently fresh matviews to optimize the execution of a query and work on "freshness" tracking are orthogonal to work on incremental maintenance. I have no plans to work on either matview freshness or rewrite, as there seems to be several years worth of work to get incremental maintenance up to a level matching other products. I welcome anyone else to take on those other projects. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
