From: | Jose' Cruanyes <cruanyes(at)cegroup(dot)it> |
---|---|
To: | Ivo Rossacher <rossacher(at)bluewin(dot)ch> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Change the character encoding of a database |
Date: | 2004-06-28 22:45:28 |
Message-ID: | DA147AD0-C954-11D8-8348-0003935B359C@cegroup.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Jun 28, 2004, at 11:38 PM, Ivo Rossacher wrote:
>
> I did try to dump the database by pgdump database > dump.dmp, droped
> the
> database, recreate it with the encoding UNICODE and restore the dump
> by psql
> database < dump.dmp which worked after some small changes (change the
> client
> encoding to UNICODE) in the dump.dmp. Without the changes in the
> dump.dmp
> there was a error message about invalide codes and no import at all.
> With the
> changes there are still some encoding mistakes (wrong signes in the
> strings)
> but the import basically works.
I've solved this changing the encoding of the dump.dmp file from ASCII
to UTF8
Pax et Bonum
# dott. Jose' Cruanyes Aguilar - C.E. Soft srl
# Pzza. Firenze,4 MILANO - XX Settembre 10, CREMONA
# 02,33603122 0372,460602
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Keller | 2004-06-28 23:03:38 | Re: Capacity Planning |
Previous Message | Jim Seymour | 2004-06-28 21:57:28 | Re: pg_ctl question |