From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
---|---|
To: | Ben Tilly <btilly(at)gmail(dot)com> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Hash index todo list item |
Date: | 2007-09-04 00:27:31 |
Message-ID: | 20070904002730.GI16568@it.is.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 03, 2007 at 05:20:34PM -0700, Ben Tilly wrote:
>
> That raises a very random thought. One of the nicer features of
> Oracle is the ability to have function-based indexes. So you could
> index, say, trim(lower(person.name)). There are a *lot* of practical
> situations where that comes in handy. The best workaround that I can
> think of for not having that is to have a column defined to hold the
> result of the function, maintain that column with a trigger, then
> index that column. Which works, but is inelegant. (It also requires
> storing completely redundant data.)
>
> Is there any prospect of postgres aquiring that functionality?
>
> Ben
>
I believe that PostgreSQL already supports functional indexes. In fact,
one suggestion to address the egregiously poor performance of the current
hash index was to replace it with a functional index.
Regards,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-09-04 00:29:28 | Re: Code examples |
Previous Message | Ben Tilly | 2007-09-04 00:20:34 | Re: Hash index todo list item |