Re: Initdb-cs_CZ.WIN-1250 buildfarm failures

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Initdb-cs_CZ.WIN-1250 buildfarm failures
Date: 2014-12-20 18:22:17
Message-ID: 5535.1419099737@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
> But clearly, something changed between RH 6.5 and 6.6, because on 6.5 I
> get this:

> $ LANG=cs_CZ.WIN-1250 locale LC_NUMERIC
> ,
>
> 3;3
> 44
> 160
> CP1250

> while on 6.6 I get this:

> $ LANG=cs_CZ.WIN-1250 locale LC_NUMERIC
> ,

> 3;3
> 44
> 160
> ANSI_X3.4-1968

That's certainly broken. The entire point of having a cs_CZ.WIN-1250
locale (as opposed to cs_CZ.something-else) would be to specify a
codeset corresponding to WIN-1250. Our code recognizes the spelling
"CP1250" for that. It's possible there are other spellings we should
recognize, but "ANSI_X3.4-1968" is certainly not one. As I said, that
just means ASCII, so it's completely useless for determining which
ASCII-superset encoding is wanted.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-12-20 18:28:33 Re: Initdb-cs_CZ.WIN-1250 buildfarm failures
Previous Message Tom Lane 2014-12-20 18:05:33 Re: Initdb-cs_CZ.WIN-1250 buildfarm failures