Noah Misch <n...@leadboat.com> writes:
> On Sun, Feb 10, 2013 at 06:47:30PM -0500, Tom Lane wrote:
>> The key problem, ISTM, is that it's not at all clear what encoding to
>> expect the incoming data to be in. I'm concerned about trying to fix
>> that by assuming it's in some "platform encoding" --- for one thing,
>> while that might be a well-defined concept on Windows, I don't believe
>> it is anywhere else.
> GetPlatformEncoding() imposes a sufficiently-portable definition. I just
> don't think that definition leads to a value that can be presumed desirable
> and adequate for postgresql.conf.
Nah, GetPlatformEncoding is utterly useless for this purpose --- restart
the server with some other environment, and bad things will happen.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
