From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving count(*) |
Date: | 2005-11-18 18:35:04 |
Message-ID: | 7711.1132338904@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2005-11-18 19:25:40 | Re: order by, for custom types |
Previous Message | Grzegorz Jaskiewicz | 2005-11-18 18:14:54 | order by, for custom types |