Re: buildfarm / handling (undefined) locales

From: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
To: "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Tomas Vondra" <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: buildfarm / handling (undefined) locales
Date: 2014-05-14 14:30:43
Message-ID: ea20ae657a4e7047e8d5a5079bf696c0.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14 Květen 2014, 16:26, Heikki Linnakangas wrote:
> On 05/14/2014 05:19 PM, Tom Lane wrote:
>
>> Anyway, given that we seem to have consensus on doing this (modulo
>> exact text of the error message), the next question is whether we
>> want to change this only in HEAD, or consider it a back-patchable
>> bug fix. I lean to the former but can see that there's some
>> argument for the latter.
>
> HEAD-only. There might be scripts out there that do initdb with invalid
> LANG. They might be perfectly happy with getting the C locale, and
> backpatching this would make them unhappy.

Not sure if 'happy with broken config' is the right argument here, but it
certainly is a behaviour change / not a bugfix, so +1 for HEAD-only from
me too.

Tomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhe-Wei Jiang 2014-05-14 14:32:51 Re: Wanna help PostgreSQL
Previous Message Zhe-Wei Jiang 2014-05-14 14:26:54 Re: Wanna help PostgreSQL