Re: foreign_data test fails with non-C locale
| От | Andrew Dunstan |
|---|---|
| Тема | Re: foreign_data test fails with non-C locale |
| Дата | |
| Msg-id | 49678659.4040904@dunslane.net обсуждение исходный текст |
| Ответ на | Re: foreign_data test fails with non-C locale ("Guillaume Smet" <guillaume.smet@gmail.com>) |
| Ответы |
Re: foreign_data test fails with non-C locale
|
| Список | 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 по дате отправления: