Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Michael Paesold <mpaesold(at)gmx(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date: 2006-01-07 22:35:33
Message-ID: 13961.1136673333@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> However, to the best of my knowledge, Windows does NOT consult the environment when set_locale is called. ISTM we probably need to call set_locale ourselves on Windows with the desired values.

We already do, during process startup. The question becomes where the
heck is Perl looking for the locale information, when on Windows?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-01-07 23:05:00 Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Previous Message Andrew Dunstan 2006-01-07 22:25:05 Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)