Hello,
iconv seemed to work fine. I converted the dump file from LATIN1 to UFT8
and kept the changes in the client_encoding (in the dump file) and loaded
them all into the database.
No complains. I still need to verify the result but at least I got no
restore errors based on character encoding.
Thanks for the tips.
Archie
> Archibald Zimonyi wrote:
>>
>> Hello,
>>
>>> Archibald Zimonyi <arsi@aranzo.netg.se> writes:
>>>> I went into the generated dump file and (more wish then anything else)
>>>> tried to simply change the encoding from LATIN1 to UTF8 and then load the
>>>> file, it did not complain about incorrect encoding setting for the load,
>>>> however it complained that the characters did not match true UTF8
>>>> characters (which was almost what I guessed would happen).
>>>
>>> Indeed. Do *not* change the client_encoding setting in the dump file.
>>> You can edit the ENCODING options in the CREATE DATABASE commands
>>> though. (Didn't we explain this to you already?)
>>>
>
>> Well, I did send this query with an incorrect email address so it
>> got stuck and was never posted properly, so I have not seen any such
>> reply. Can you please explain again?
>
> Search the archives: http://archives.postgresql.org/
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
