| 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:14:35 |
| Message-ID: | 51E9BC86-5CD2-4060-A747-8EF1FC8DED4E@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2005-11-22, at 16:39, Martijn van Oosterhout wrote:
> On Tue, Nov 22, 2005 at 04:24:21PM +0100, Grzegorz Jaskiewicz wrote:
>>> Translation: you do know how to define a sortable order (ie,
>>> generate
>>> the text version and compare); you're just too lazy to create the
>>> operators to do it ...
>> We do have WORKING < , > , etc operators, and ::text cast already.
>> Thing is, can I have btree and gist indexes at the same time ?
>
> Sure, did you look at the ltree example someone pointed you to?
>
> Have a nice day,
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.
Thanks folks.
--
GJ
"If we knew what we were doing, it wouldn't be called Research, would
it?" - AE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-11-22 16:17:50 | Re: order by, for custom types |
| Previous Message | Martijn van Oosterhout | 2005-11-22 16:14:33 | Re: Practical error logging for very large COPY |