Skip site navigation (1) Skip section navigation (2)

Re: Reverse-sort indexes and NULLS FIRST/LAST sorting

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Reverse-sort indexes and NULLS FIRST/LAST sorting
Date: 2007-01-02 15:12:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> I'd like to see this implemented with more general collation support in 
>> mind.
> I'm really not prepared to buy into that, simply because it puts ICU or
> some equivalent large chunk of new code into the critical path to finish
> what I'm doing.  ...

Yeah, I didn't mean doing that right now. Just to keep it in mind so 
that what we do now fits in nicely with it in the future.

>> The NULLS FIRST/LAST support, as well as ascending and descending 
>> orderings would be special cases of the general collation and collation 
>> conversion machinery.
> That seems like a bad idea, because nulls first/last and asc/desc
> ordering are valid concepts for all btree-indexable datatypes, whereas
> collation is only meaningful for text.  Besides, that approach just
> moves the bloat over from too-many-opclasses to too-many-collations; do
> we really want to need four collation objects for each basic collation?

Hmm, I guess we don't.

   Heikki Linnakangas

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-01-02 15:18:30
Subject: Re: [PATCHES] xlog directory at initdb time
Previous:From: Andrew DunstanDate: 2007-01-02 15:04:43
Subject: Re: Status of Fix Domain Casting TODO

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group