Re: lc_collate issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cody Pisto <cpisto(at)rvweb(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: lc_collate issue
Date: 2007-08-24 20:16:37
Message-ID: 5091.1187986597@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Cody Pisto <cpisto(at)rvweb(dot)com> writes:
> I'm looking for any kind of a reason (and potential workarounds), be it
> bug or otherwise, why the following two queries produce different
> results under a database encoding of UTF8 and lc_collate of en_US.UTF-8:

That's just how it is in most non-C locales --- they use some weird
algorithm that's alleged to approximate what dictionary makers
traditionally do with phrases. I don't recall the details but there's
something about multiple passes with spaces being ignored in earlier
passes. You'll find that sort(1) sorts these lines the same way.

If you don't like it, use C locale, or put together your own locale
definition. (No, I'm not sure how hard that is ...)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Cody Pisto 2007-08-24 20:47:15 Re: lc_collate issue
Previous Message Vivek Khera 2007-08-24 20:15:52 Re: PostgreSQL vs Firebird feature comparison finished