Re: Collation at database level

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Radek Strnad" <radek(dot)strnad(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Collation at database level
Date: 2008-04-16 12:48:47
Message-ID: 87zlruvuc0.fsf@oxford.xeocode.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Radek Strnad" <radek(dot)strnad(at)gmail(dot)com> writes:

> The problem with POSIX locales is that you never know what
> locales user have got installed. I've discovered that some linux distros
> don't even have other than UTF-8 based locales.

On Debian you're even deeper in it. The user can configure which locales he's
actually interested in having on a machine. They're listed in /etc/locale.gen
but I wouldn't suggest looking there. I think you have to try switching
locales and see if setlocale returns NULL.

> Because of ANSI defines collations deffined by ISO-8859-1 and UTF-* we need
> to somehow implement these collations.

These are encodings. What ANSI spec are you referring to, SQL? What does it
actually say?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-04-16 13:09:38 Re: Improve shutdown during online backup
Previous Message Radek Strnad 2008-04-16 12:36:03 Collation at database level