| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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:04:08 |
| Message-ID: | 10883.1424541848@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-02-21 18:09:59 | Re: Query Rewrite with Postgres' materialized views |
| Previous Message | Robert Haas | 2015-02-21 17:43:06 | Re: Query Rewrite with Postgres' materialized views |