| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | 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 15:02:30 |
| Message-ID: | 18624.1400079750@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> As far as Windows goes, we could certainly use #ifdef WIN32 to print
> some different text, if anyone can write down what it should be.
Some googling suggests that on Windows, setlocale pays no attention
to environment variables but gets a value that the user can set via
the Control Panel. This probably means that an invalid setting is
impossible, or at least that we have no clear idea how the user could
screw it up. So I'm thinking we do not need a Windows-specific
phrasing of the message, until such time as we see evidence of how
you could provoke this case on Windows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2014-05-14 15:06:55 | Re: popen and pclose redefinitions causing many warning in Windows build |
| Previous Message | Heikki Linnakangas | 2014-05-14 14:51:24 | Re: popen and pclose redefinitions causing many warning in Windows build |