From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Eric Grinstein <ericgrinstein(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Query Rewrite with Postgres' materialized views |
Date: | 2015-02-21 18:09:59 |
Message-ID: | CA+TgmoYXJ3oppuVdUSrTr5hewj1R7a1BmzZKsZdwGjPAWAeWnA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 21, 2015 at 1:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I'm not really sure what Josh was talking about in that answer. In
>> terms of doing this automatically, I doubt that's likely to happen
>> until we have a way to automatically update a materialized view when
>> the underlying data changes --- and Kevin Grittner has done a bunch of
>> work towards that, but more is needed to get us there.
>
> Even with auto maintenance, it seems unlikely that matviews would ever
> be so transparent that it would be okay for the planner to automatically
> substitute them into a query. The data in a matview is going to be at
> least a little bit stale, else You're Doing It Wrong.
Perhaps, but this is a feature we've gotten MANY customer requests
for. IDK why, but it's true.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-02-21 18:20:04 | Re: Bootstrap DATA is a pita |
Previous Message | Tom Lane | 2015-02-21 18:04:08 | Re: Query Rewrite with Postgres' materialized views |