Re: BUG #4276: Feature request aggregate indexes

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4276: Feature request aggregate indexes
Date: 2008-07-08 14:24:07
Message-ID: 1215527047.4051.900.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Tue, 2008-07-01 at 13:27 +0000, x wrote:
> The following bug has been logged online:
>
> Bug reference: 4276
> Logged by: x
> Email address: noreply(at)postgresql(dot)org
> PostgreSQL version: n/a
> Operating system: n/a
> Description: Feature request aggregate indexes
> Details:
>
> # CREATE INDEX count_star ON fscrbank (COUNT(*));
> ERROR: cannot use aggregate function in index expression
>
> Don't know how the architechture would handle it but this should be
> possible.

The developers agree this is a good idea. It is already on the TODO,
described as "materialized views", though I like your name for it also,
since that is the main use case.
http://www.postgresql.org/docs/faqs.TODO.html

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message crystal 2008-07-09 08:11:30 BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Previous Message Tom Lane 2008-07-08 14:20:55 Re: BUG #4286: ORDER BY returns inconsistent results when using LIMIT on a integer column set to default values