Re: buildfarm / handling (undefined) locales

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: buildfarm / handling (undefined) locales
Date: 2014-05-15 00:30:01
Message-ID: 21691.1400113801@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:
> On 13.5.2014 23:07, Tom Lane wrote:
>> Attached is a draft patch that behaves like this:
>>
>> $ initdb --locale=foo
>> The files belonging to this database system will be owned by user "postgres".
>> This user must also own the server process.
>>
>> initdb: invalid locale name "foo"

> I see the committed patch actually behaves like this:

> initdb: invalid locale name "cs_CZ.WIN-1250"
> The files belonging to this database system will be owned by user
> "pgbuild".
> This user must also own the server process.

> (at least that's what magpie logged at [1]). I find that confusing,

Interesting. I guess stdout isn't getting fflush'd soon enough when
it's going to a file. We should probably mark it as line-buffered
so the behavior is consistent with the interactive case.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-05-15 00:42:26 Re: [PATCH] Writing changes of decoding plugin in the memory context where data is kept?
Previous Message Tomas Vondra 2014-05-15 00:19:36 Re: buildfarm / handling (undefined) locales