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

Re: Issues with LC_COLLATE, across 8.3/8.4 on various platforms

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Issues with LC_COLLATE, across 8.3/8.4 on various platforms
Date: 2010-02-03 19:16:36
Message-ID: 1265224596.16965.1.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-admin
On ons, 2010-02-03 at 17:05 +0200, Achilleas Mantzios wrote:
> Στις Wednesday 03 February 2010 16:53:20 ο/η Peter Eisentraut έγραψε:
> > On tis, 2010-02-02 at 17:28 +0200, Achilleas Mantzios wrote:
> > > It seems that libc's behaviour regarding LC_COLLATE in Linux/FreeBSD
> > > are two different stories, hence the seen results.
> > 
> > The UTF-8 locales on FreeBSD and Mac OS X are pretty much broken.
> > 
> > This is becoming a FAQ ...
> 
> This is a libc/locale combination issue. Care to elaborate?
> AFAICT for my case in FreeBSD, the greek UTF locale el_GR.UTF-8 behaves as expected without problems.

Well,

"""
while in all of
PostgreSQL 8.3.3 on i686-pc-linux-gnu (lc_collate=C)
PostgreSQL 8.3.7 (lc_collate=el_GR.UTF-8) on i386-unknown-freebsd6.3 
PostgreSQL 8.4.1 on x86_64-unknown-freebsd8.0 (lc_collate=en_US.UTF-8),
gives
        fooname
-------------------------
 Cylinder Liner No1
 Cylinder head No1
 Cylinder head cover No1
"""

is not a correct sorting result in my book, unless your measure of
correctness is ASCII byte value order.  And then it's left as an
exercise to determine what the results would be for texts involving
non-ASCII letters.



In response to

Responses

pgsql-admin by date

Next:From: Campbell, LanceDate: 2010-02-03 21:12:59
Subject: How to clear log files
Previous:From: Achilleas MantziosDate: 2010-02-03 15:05:35
Subject: Re: Issues with LC_COLLATE, across 8.3/8.4 on various platforms

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