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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: JP Glutting <jpglutting(at)oqua(dot)udl(dot)es>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Bug? was: Re: ERROR: could not convert UTF8 character to ISO8859-1
Date: 2006-03-27 15:38:10
Message-ID: 14636.1143473890@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

JP Glutting <jpglutting(at)oqua(dot)udl(dot)es> writes:
> This is reproducible, and I think it is a bug, because I have the
> problem not only with data backed up from Postgres 8.0 and restored to
> Postgres 8.1, but with data generated in Postgres 8.1. It is
> reproducible, at least on Windows XP. Here is a table that I backed up
> from Postgres 8.0. It can be restored into a Postgres 8.0 or 8.1
> database, but it cannot then be backed up in Postgres 8.1.

The error message seems perfectly clear to me: you've got a character in
that table that has no representation in LATIN1. The difference between
8.0 and 8.1 behavior is probably because you're somehow using different
client_encoding settings in the two cases.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2006-03-27 16:43:20 Re: Advantages of PostgreSQL over MySQL 5.0
Previous Message Tom Lane 2006-03-27 15:22:49 Re: [GENERAL] PANIC: heap_update_redo: no block