Re: WIP patch: Collation support - Mailing list pgsql-hackers

From Dave Page
Subject Re: WIP patch: Collation support
Date
Msg-id 937d27e10809230326g168a7559r5609a2f2b0fda8b7@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch: Collation support  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, Sep 23, 2008 at 10:20 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> Committed.

*adds yet another item to his pgAdmin todo list* :-(

> Tom Lane wrote:
>>
>> * You should try to get rid of LOCALE_NAME_BUFLEN altogether.  Definitely
>> the comment about it in pg_control.h is now obsolete.
>
> Yep. I removed LOCALE_NAME_BUFLEN. The real max length of a locale name is
> now NAMEDATALEN, because it's stored in a name field in pg_database.
> NAMEDATALEN is only 64 bytes, whereas LOCALE_NAME_BUFLEN was 128. 64 bytes
> should be enough for "en_GB.UTF8" style locale names, but I wonder if it's
> enough for the longer names used on Windows? Could someone confirm that,
> please?

The longest I can find is:

Serbian (Cyrillic)_Bosnia and Herzegovina

at 42 characters.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: WIP patch: Collation support
Next
From: Martijn van Oosterhout
Date:
Subject: Re: WIP patch: Collation support