From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Eric Grinstein <ericgrinstein(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Query Rewrite with Postgres' materialized views |
Date: | 2015-02-21 17:43:06 |
Message-ID: | CA+TgmoZr5jE0mfqvkJa=kKbGN5kGiOf2N95xwbUR3xs7cotDZg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Feb 15, 2015 at 10:05 PM, Eric Grinstein
<ericgrinstein(at)gmail(dot)com> wrote:
> Are there any plans for implementing query rewriting (i.e. allowing the
> optimizer to substitute materialized views for queries)
> in upcoming versions? I have recently seen this answer, saying that query
> rewriting could be achieved using the rules system, but
> I could not figure out how to. Could someone please give me some tips on how
> to do it? Is it possible to make a rule not to all SELECTs of a table but
> for a specific query? Or the trick is done with another approach?
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-02-21 18:04:08 | Re: Query Rewrite with Postgres' materialized views |
Previous Message | Tom Lane | 2015-02-21 16:43:32 | Re: Bootstrap DATA is a pita |