Re: LC_COLLATE and index usage

From: Dennis Gearon <gearond(at)cvc(dot)net>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LC_COLLATE and index usage
Date: 2003-05-08 00:16:58
Message-ID: 3EB9A1FA.555C4BA7@cvc.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Personally,
I'd like to see LOCALE done away with, everything be in UTF-8, and have
a POSGRES extension that sets the sort order as an itemized listing of
mime type languages like:

SET COLLATION( en-us, fr, ru ).

Everything NOT in those character sets, falls below them in the sort
order, but stays in it's tabular order, otherwise.

PS. We are sure lucky in the western world that we have such a
simplistic alphabet.

Karsten Hilbert wrote:
>
> > According to the postgres 7.3.2 docs, initializing a database cluster
> > with LC_COLLATE set to anything other than "C" will disable the use of
> > indexes during LIKE searches. This presents a bit of a problem for
> > me, since the client application I'm writing uses LIKE searches and
> > ships internationally. As I understand it, I can have good
> > performance, or locale-specific ORDER BY output, but not both. Is
> > there a plan to remove this limitation?
> Question seconded (and tacit suggestion for a TODO item) on
> behalf of GnuMed (www.gnumed.org)
>
> Karsten Hilbert, MD
> --
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2003-05-08 00:20:15 Re: Many little databases or one big one?
Previous Message Steve Crawford 2003-05-08 00:13:51 Re: age() and date intervals