Re: [GENERAL] Encoding problem using pg_dumpall - Mailing list pgsql-admin

From Tom Lane
Subject Re: [GENERAL] Encoding problem using pg_dumpall
Date
Msg-id 7403.1233250794@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Encoding problem using pg_dumpall  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [GENERAL] Encoding problem using pg_dumpall  (Magnus Hagander <magnus@hagander.net>)
List pgsql-admin
Magnus Hagander <magnus@hagander.net> writes:
> Tom Lane wrote:
>> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch,
>> which seems like an oversight.  So you need to fix your locale,
>> or else use pg_dump directly.)

> IIRC, you can't set the windows console to be UTF8.

Ugh.  That seems to raise the priority of having a -E switch quite
a lot.  I'm surprised no one has complained of this before.

I think it should be possible to work around it by setting
PGCLIENTENCODING in the environment, but I dunno how to do that
on Windows.

            regards, tom lane

pgsql-admin by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
Next
From: Magnus Hagander
Date:
Subject: Re: [GENERAL] Encoding problem using pg_dumpall