Re: [GENERAL] Encoding problem using pg_dumpall

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Moshe Ben-Shoham <mosheb(at)nexperience(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
Date: 2009-01-29 17:39:54
Message-ID: 7403.1233250794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Magnus Hagander 2009-01-29 17:45:25 Re: [GENERAL] Encoding problem using pg_dumpall
Previous Message Magnus Hagander 2009-01-29 17:31:49 Re: [GENERAL] Encoding problem using pg_dumpall

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2009-01-29 17:40:31 Re: Pet Peeves?
Previous Message Gabi Julien 2009-01-29 17:39:01 Re: New 8.4 hot standby feature