Re: foreign_data test fails with non-C locale - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: foreign_data test fails with non-C locale
Date
Msg-id 49678659.4040904@dunslane.net
Whole thread Raw
In response to Re: foreign_data test fails with non-C locale  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Responses Re: foreign_data test fails with non-C locale  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers

Guillaume Smet wrote:
> On Fri, Jan 9, 2009 at 5:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>   
>> However, the
>> de facto policy is that we try to keep them passing in locales that
>> are used by any of the regular developers.  I think it would be useful
>> to have buildfarm members testing in a few common locales.
>>     
>
> If you define common locales, I can set up as many new animals as
> needed to cover the locales needed for any branch we'd like to test.
>
> Perhaps we should add a parameter to the buildfarm config file so that
> the buildfarm script can check the locale is accepted and set it
> directly. Considering that we won't have the locale information in the
> animal description, it's a good way to have it in the report.
>
>
>   

Sure, we can easily have buildfarm's initdb step set any locale (and 
encoding, for that matter) we like. That's a simple change.

cheers

andrew


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: New patch for Column-level privileges
Next
From: Richard Huxton
Date:
Subject: Re: Improving compressibility of WAL files