| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: comparing index columns |
| Date: | 2007-06-13 09:54:01 |
| Message-ID: | 466FBEB9.7090505@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
>> I don't have much insight into the operator classes and operator families
>> and how they work. Where should I look for the related code ?
>
> Primary opclass members are stored right in the Relation data struct for
> you. Since (I trust) you're only supporting this for btree, you could
> just use rd_supportinfo[0] which will not even cost an fmgr lookup.
> See index_getprocinfo() and callers.
There's currently no reason to limit HOT to b-trees.
How about just doing a memcmp? That would be safe, simple and fast and
covers all interesting use cases.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas ADI SD | 2007-06-13 09:55:25 | Re: Selecting a constant question: A summary |
| Previous Message | Gregory Stark | 2007-06-13 09:36:28 | Re: Selecting a constant question: A summary |