Re: Collation rules and multi-lingual databases - Mailing list pgsql-general

From Greg Stark
Subject Re: Collation rules and multi-lingual databases
Date
Msg-id 87isosj9iu.fsf@stark.dyndns.tv
Whole thread Raw
In response to Re: Collation rules and multi-lingual databases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Collation rules and multi-lingual databases  (Dennis Gearon <gearond@fireserve.net>)
List pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Greg Stark <gsstark@mit.edu> writes:
> > My understanding is that the entire set of localization parameters needs to be
> > decided upon when the initdb is done and can never be changed later. Is that
> > right?
>
> No, not all of them are frozen.  Unfortunately, the one you care about
> (LC_COLLATE) is.  The reason for this is that it determines index
> ordering for textual columns, and so changing LC_COLLATE on the fly
> produces instant corrupt indexes :-(

Yeah, I really would be perfectly happy to have indexes be in "C" order and
have my queries have to specifically specify the sort order in the ORDER BY
clause, knowing they won't use the index.

Well, ok, not quite perfectly happy. But in this case there are no indexes on
the columns anyways so...

> A solution for this is on the TODO list, but don't hold your breath ...

--
greg

pgsql-general by date:

Previous
From: "Nigel J. Andrews"
Date:
Subject: Re: Mail server load
Next
From: Tom Lane
Date:
Subject: Re: Buglist