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

Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN
Date: 2011-03-22 21:44:06
Message-ID: AANLkTimBCCiLW__CN8yNfHEoqAuz5zOGKU=VMXhF3awu@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Tue, Mar 22, 2011 at 7:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Throw error for indeterminate collation of an ORDER/GROUP/DISTINCT target.
>

hmm. In the current arrangement = doesn't depend on collation, right?
So in an ideal world we could use any collation we want to implement
GROUP/DISTINCT/UNION/INTERSECT/EXCEPT. I can see how it would be hard
to generate paths for every possible collation but it would be awfully
nice if we had a way to represent this so we could pick whichever
index we thought would be fastest instead of relying on the user to
select one.

-- 
greg

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-03-22 21:47:55
Subject: Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN
Previous:From: Tom LaneDate: 2011-03-22 21:44:04
Subject: Re: Flex output missing from 9.1a4 tarballs?

pgsql-committers by date

Next:From: Tom LaneDate: 2011-03-22 21:47:55
Subject: Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN
Previous:From: Tom LaneDate: 2011-03-22 21:21:06
Subject: pgsql: Make initdb ignore locales for client-only encodings.

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