| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:31:49 |
| Message-ID: | 4981E805.7040302@hagander.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Tom Lane wrote:
> "Moshe Ben-Shoham" <mosheb(at)nexperience(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-29 17:39:54 | Re: [GENERAL] Encoding problem using pg_dumpall |
| Previous Message | Tom Lane | 2009-01-29 15:16:16 | Re: [GENERAL] Encoding problem using pg_dumpall |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Long | 2009-01-29 17:32:53 | Re: Pet Peeves? |
| Previous Message | Sebastian Tennant | 2009-01-29 17:30:25 | Recovery mode |