| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin McArthur <Kevin(at)StormTide(dot)ca>, andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: order by, for custom types |
| Date: | 2005-11-22 16:23:16 |
| Message-ID: | 6D092A8C-B5CF-4F9E-AF6E-D601C2A2696C@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2005-11-22, at 17:17, Martijn van Oosterhout wrote:
> On Tue, Nov 22, 2005 at 05:14:35PM +0100, Grzegorz Jaskiewicz wrote:
>> Ok, I hacked btree for my type, and surely I can have both btree and
>> gist at the same time on the same column.
>> /me is now going to have a look on btree_gist.
>
> You don't actually have to have a btree defined on your column for
> ORDER BY to work, you just need to define a btree OPERATOR CLASS so
> that PostgreSQL knows what you mean by "ORDER BY".
yep, I know. Thanks.
Anyhow, I wanted to see if having two indexes will make it faster/
slower. and if it is possible in first place.
--
GJ
"If we knew what we were doing, it wouldn't be called Research, would
it?" - AE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gevik | 2005-11-22 16:26:23 | Re: TODO item "%Allow pg_hba.conf be controlled via |
| Previous Message | Greg Stark | 2005-11-22 16:23:00 | Re: Practical error logging for very large COPY |