| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-03-04 00:27:02 |
| Message-ID: | 5133EA56.2050103@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
> There's a much more fundamental reason why this will never happen, which
> is that the query planner is not licensed to decide that you only want
> an approximate and not an exact answer to your query.
I think it would be worth talking about when someone wants to implement
it. I'd imagine it would require setting a GUC, though, which would be
off by default for obvious reasosn.
> If MVs were guaranteed always up-to-date, maybe we could think about
> automatic use of them --- but that's a far different feature from what
> Kevin has here.
And of limited utility, as mentioned.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-04 00:32:42 | pgsql: Fix map_sql_value_to_xml_value() to treat domains like their bas |
| Previous Message | Kevin Grittner | 2013-03-04 00:25:13 | pgsql: Add a materialized view relations. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-04 00:34:02 | Re: is it bug? - printing boolean domains in sql/xml function |
| Previous Message | Tom Lane | 2013-03-04 00:07:39 | Re: CREATE RULE "_RETURN" and toast tables |