Re: Query Rewrite with Postgres' materialized views
| От | Eric Grinstein |
|---|---|
| Тема | Re: Query Rewrite with Postgres' materialized views |
| Дата | |
| Msg-id | CAK7uWEzk1CEntDstCu93T4vYh5cSydHKQMk2MY=e32wsve2ymw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Query Rewrite with Postgres' materialized views (Robert Haas <robertmhaas@gmail.com>) |
| Список | pgsql-hackers |
Thank you for your answers.
I am very eager to contribute to Postgres, especially in the materialized views area.
I have created a thread proposing to work on it as my Google Summer of Code project.
It became a consensus that implementing the query rewrite feature would be unfeasible
for such a short period of time, but Tomas Vondra suggested I could work on a first part of It, such as
making a staleness flag for the MVs. If you have any opinions on the thread, i'd be pleased to read them.
Thank you and regards,
Eric
2015-02-21 16:09 GMT-02:00 Robert Haas <robertmhaas@gmail.com>:
Perhaps, but this is a feature we've gotten MANY customer requestsOn Sat, Feb 21, 2015 at 1:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.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.
for. IDK why, but it's true.
В списке pgsql-hackers по дате отправления: