Re: fixes for the Danish locale

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fixes for the Danish locale
Date: 2016-07-21 19:53:45
Message-ID: 57912849.2060109@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/21/2016 02:26 PM, Greg Stark wrote:
> On Thu, Jul 21, 2016 at 5:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Confirmed here. Will deal with it, but I wonder why we have no buildfarm
>> members covering this ...
> We're not going to have a build farm member for every locale the local
> systems support.
>
> Perhaps the build farm script should pick a random locale for each
> run. Either a random locale from the set on the OS or a random
> language from a list of locale that the regression tests are intended
> to be safe for.
>

I don't see why we shouldn't have a buildfarm machine that tests a very
large number of locales. It takes a very lightly resourced machine like
nightjar just over two minutes per locale. The list of locales to test
is a setting in the config file.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2016-07-21 19:59:31 Re: pg_restore & search_path, COPY failed for table "mytable": ERROR: function myinnerfunction(integer) does not exist
Previous Message Peter Geoghegan 2016-07-21 18:54:18 Re: fixes for the Danish locale