From: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Moshe Ben-Shoham <mosheb@nexperience.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
Date: Thu, 29 Jan 2009 18:31:49 +0100
Message-ID: <4981E805.7040302@hagander.net> (raw)
In-Reply-To: <28817.1233242176@sss.pgh.pa.us>
References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com>
<28817.1233242176@sss.pgh.pa.us>
Tom Lane wrote:
> "Moshe Ben-Shoham" <mosheb@nexperience.com> writes:
>> C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
>> c:\temp\dbdump.sql
>> pg_dump: SQL command failed
>> pg_dump: Error message from server: ERROR: character 0xd595 of encoding
>> "UTF8" has no equivalent in "WIN1252"
>
> Apparently you have WIN1252 set as the default client encoding, probably
> via an environment variable or locale setting. Either get rid of it,
> or override it by including "-E UTF8" in the pg_dump command.
>
> (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. Thus, your option is
to switch to using pg_dump and use -E UTF8 on that one.
//Magnus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: magnus@hagander.net, tgl@sss.pgh.pa.us, mosheb@nexperience.com, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
In-Reply-To: <4981E805.7040302@hagander.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox