Re: Bug #620: create index ... (date_part('year', d)) fails - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: Bug #620: create index ... (date_part('year', d)) fails
Date
Msg-id 20020315082549.D50245-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Bug #620: create index ... (date_part('year', d)) fails  (pgsql-bugs@postgresql.org)
List pgsql-bugs
sszabo@bigpanda.com

On Fri, 15 Mar 2002 pgsql-bugs@postgresql.org wrote:

> Ernst Molitor (molitor@uni-bonn.de) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> create index ... (date_part('year', d)) fails
>
> Long Description
> IMHO, creation of an index on a part of a date field should work,
> but it fails due to the definition of "create index ..." in gram.y.
>
> Maybe I'm wrong, but I feel that for large tables which will have to
> be analyzed per year, an index of this kind could be an advantage.

You need to make a function that is marked iscachable that returns
date_part('year', <argument>) and use that.  IIRC, functional indices
require that all of the arguments be column references.

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Bug #619: Not possible to specify foreign key name
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #621: why postgreSQL stored databases in digital filenames?