Re: ERROR: could not convert UTF8 character to ISO8859-1

From: JP Glutting <jpglutting(at)oqua(dot)udl(dot)es>
To:
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: could not convert UTF8 character to ISO8859-1
Date: 2006-03-23 15:37:48
Message-ID: 4422C0CC.2060507@oqua.udl.es
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

More information. I backed up a database (one that failed to backup in
8.1) from the old 8.0 system, and re-imported it into the 8.0 system
without any problem. Then I imported it into the 8.1 system without
errors, and tried to do a backup again. It failed.

So there seems to be either a flaw in the 8.1 system, or perhaps a
problem with the way 8.0 backs up it's data which only shows up when
imported into the newer system.

Right now I need the data I have in the 81 system, and I can't back it
up except by shutting down Postgres and copying the whole /data
directory. I think I am going to try to go back to 8.0. Is it a very bad
idea to shut down Postgres and try to replace the data directory for 8.0
withe the data directory for 8.1?

Any help or suggestions appreciated.

JP

JP Glutting wrote:

> To answer my own mail, I shut down the 8.1 database, and started up
> the 8.0 PostgreSQL install that is still on my computer, and the
> backups work fine. I do get the message about how 8.1 handles sorting
> of unicode characters more correctly, but looking at my backups, I can
> see that the full back up failed about the time that I switched to the
> newer version.
>
> Is there a fix for this? Is this a bug? Is there a workaround?
>
> Thanks for any help.
>
> JP
>
> JP Glutting wrote:
>
>> I have seen several people with this same error. I get mine when
>> trying to backup using pg_dump, causing my backups to fail.
>>
>> I am using PostgreSQL 8.1 on Windows XP.The databases are in UTF8. I
>> get the same error from the command line and using pgadmin3.
>>
>> Has anyone found a solution for this? Looking around online, I see
>> that this supposedly codes for a lowercase a with a circumflex (which
>> I don't have in tha table thet triggeres the error), but that this
>> may be the first part of a three-byte sequence that codes for
>> something else.
>>
>> Does anyone know of a way to pinpoint the character in the database?
>> I am not sure how to search for a raw unicode character through psql
>> or pgadmin...
>>
>> Thanks for any help!
>>
>> JP
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 1: if posting/reading through Usenet, please send an appropriate
>> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>> message can get through to the mailing list cleanly
>
>
>
>

--
____________________________________________________

Oficina de Qualitat Tel: 973 703 103
Universitat de Lleida Fax: 973 702 036

Pl. Víctor Siurana, 1
25003 Lleida
____________________________________________________

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bjørn T Johansen 2006-03-23 16:09:52 Re: Logging of sql statements?
Previous Message denis 2006-03-23 15:24:27 Interval regression test failing with -march=pentium4