From: Dario V. Fassi <software@sistemat.com.ar>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Oliver Jowett <oliver@opencloud.com>
To: pgsql-sql@postgresql.org, "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Subject: Re: [ADMIN] Migrate postgres databases from SQL_ASCII to UNICODE
Date: Sat, 17 Jul 2004 20:26:17 -0300
Message-ID: <40F9B599.6080205@sistemat.com.ar> (raw)
In-Reply-To: <16994.1090099096@sss.pgh.pa.us>
References: <40F98613.1060405@sistemat.com.ar>
<16994.1090099096@sss.pgh.pa.us>
Tom Lane wrote:
>"Dario V. Fassi" <software@sistemat.com.ar> writes:
>
>
>>A simple question, we need to migrate many (>20) postgres databases from
>>SQL_ASCII encoding to UNICODE encoding, over a 7.3.6 server.
>>
>>
>
>SQL_ASCII is not an encoding (it's more like the absence of knowledge
>about an encoding). What is the data actually stored as?
>
>
>>With Dump/Restore , we get an error (Invalid Unicode) in any field that
>>has a 8 bits character coming from the SQL_ASCII , even setting the
>>client_encoding to WIN, ISO-8859-1, and others encodings.
>>
>>
>
>It might work to just UPDATE pg_database to set datencoding to the
>correct value reflecting what you have actually stored. You might then
>need to REINDEX any indexes on textual columns, but I don't think
>anything else would go wrong.
>
>If you have a mishmash of different encodings in a single database, then
>of course there is no simple solution; you are in for some pain while
>you try to fix the data.
>
>
Yes you are right , the original data come from a DB2 with CodePage
IBM-850 and was inserted without complains in a Postgres 7.3.6 with
SQL_ASCII.
Now we are in a Jail , because IBM-850 , isn't WIN, isn't ISO-xx ,
isn't no one postgresql's encoding.
So when in change via pg_databases the encoding , 8 bits characters
become garbage.
More even if we accept this garbage chars and we set encoding to e.g.
ISO-8859-1 it's impossible go to a UNICODE because this garbage chars
are invalid in client's encoding , so they are reject (in translation
process as invalid unicode chars).
We are in a big problem, and the only way out I can imagine is fix the
data by hand :-! .
Dario,
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-sql@postgresql.org
Cc: software@sistemat.com.ar, tgl@sss.pgh.pa.us, oliver@opencloud.com, pgsql-jdbc@postgresql.org
Subject: Re: [ADMIN] Migrate postgres databases from SQL_ASCII to UNICODE
In-Reply-To: <40F9B599.6080205@sistemat.com.ar>
* 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