Re: Initdb-cs_CZ.WIN-1250 buildfarm failures

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Initdb-cs_CZ.WIN-1250 buildfarm failures
Date: 2014-12-20 18:48:23
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 20.12.2014 19:35, Tom Lane wrote:
> Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
>> On 20.12.2014 19:05, Tom Lane wrote:
>>> I am betting that you recreated them differently from before.
>> Aaaaand you're probably right. Apparently, I recreated them like this:
>> $ localedef -v -c -i cs_CZ -f WIN-1250 cs_CZ.WIN-1250
>> but the correct way seems to be this:
>> $ localedef -v -c -i cs_CZ -f CP1250 cs_CZ.WIN-1250
> Interesting. Apparently, instead of failing outright on an unrecognized
> charmap name, localedef just substituted ASCII and plowed ahead. Bad dog.

Not really. It's rather about abusive owner of the dog, using '-c' to
force the dog to create the locale even when there are warings:

# localedef -i cs_CZ -f WIN-1250 cs_CZ.WIN-1250
character map file `WIN-1250' not found: No such file or directory
no output file produced because warnings were issued

In my defense, I've been using verbose mode, and that produces a lot of
warnings like 'non-symbolic character value should not be used' (which
gets ignored in non-verbose mode) and thus missed the one important one.


In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-12-20 19:10:02 Re: PATCH: decreasing memory needlessly consumed by array_agg
Previous Message Tom Lane 2014-12-20 18:35:28 Re: Initdb-cs_CZ.WIN-1250 buildfarm failures