Re: MULTISET and additional functions for ARRAY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: MULTISET and additional functions for ARRAY
Date
Msg-id 5094.1289849916@sss.pgh.pa.us
Whole thread Raw
In response to Re: MULTISET and additional functions for ARRAY  (David Fetter <david@fetter.org>)
List pgsql-hackers
David Fetter <david@fetter.org> writes:
> On Mon, Nov 15, 2010 at 10:13:40AM -0500, Tom Lane wrote:
>> Itagaki Takahiro <itagaki.takahiro@gmail.com> writes:
>>> Another issue for sorting is that we have 4 kinds of sorting: ASC/DESC
>>> and NULLS FIRST/LAST.

>> We have a lot more kinds than that.  See USING.

> USING pretty much gives us no chance of optimizing at all.  Could we
> maybe see about optimizing the 99% case, which those two bits cover?

The question is why support more than *one* kind, if you're only
supporting a subset.  I don't see the value of messing with stuff like
NULLS FIRST if you're not going to go all the way.  What's more, the
alleged use for this is strictly as an internal optimization in multiset
representation, so there's no reason to support more than one sort
order.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Instrument checkpoint sync calls
Next
From: Tom Lane
Date:
Subject: Re: Re: Rethinking hint bits WAS: Protecting against unexpected zero-pages: proposal