From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving count(*) |
Date: | 2005-11-18 20:03:36 |
Message-ID: | 20051118200335.GD26861@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
> > Might it be possible to apply rule-style rewriting to a clause of an
> > ordinary select query? That is, is it prohibitively expensive to get PG
> > to recognise
> > SELECT count(*) FROM big_table
> > and replace it with
> > SELECT sum(summary_count) FROM my_materialised_view
>
> > This should allow you to have where-clauses and apply to a range of
> > cases. What I fear is that checking to see if the rule applies will cost
> > too much on all those queries where it doesn't apply.
>
> There is already code in the optimizer that does similar rewriting
> for min/max queries. However, that's a hard-wired transformation.
> I don't see any very simple way to provide a user-configurable
> equivalent.
I guess there must be a query-rewriting mechanism for implementing
materialized views. With that in place we may be able to implement this
other thing ... Is anybody working on materialized views?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-11-18 21:07:41 | Re: Bug in predicate indexes? |
Previous Message | Martijn van Oosterhout | 2005-11-18 20:03:25 | Re: someone working to add merge? |