From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Hari Sankar A <hsshanthamhari(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problem with PostgreSQL string sorting |
Date: | 2017-02-15 17:58:18 |
Message-ID: | 18267.1487181498@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Wed, Feb 15, 2017 at 9:05 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I believe most versions of libc use declarative specifications of locale
>> properties, so if you wanted to spend some time learning the language in
>> which those are written, you could make and install a locale that acts
>> like you want. It's possible there's one out there already, because
>> a lot of people seem to want that.
> True. And, the declarative language glibc uses doesn't look that
> complicated to me. However, you'd really have to vendor your own glibc
> to make this work, since they are compiled to some binary
> representation when glibc is built. That's probably prohibitively
> complicated to manage.
Really? "man localedef" certainly gives the impression that you can
just compile some more locales if you want. Admittedly, your system's
package manager might have a hissy fit about nonstandard files
suddenly appearing in /usr/lib/locale, but that's not glibc's fault.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-02-15 18:15:10 | Re: Problem with PostgreSQL string sorting |
Previous Message | Hari Sankar A | 2017-02-15 17:26:47 | Re: Problem with PostgreSQL string sorting |