On Mon, Mar 27, 2006 at 10:20:23AM +0000, JP Glutting wrote:
> The following bug has been logged online:
> Bug reference: 2360
> Logged by: JP Glutting
> Email address: jpglutting(at)oqua(dot)udl(dot)es
> PostgreSQL version: 8.1 (8.0)
> Operating system: Windows XP SP2
> Description: Backup produces "ERROR: could not convert UTF8 character
> to ISO8859-1"
> There seems to be a bug in version 8.1 that produces this error when doing a
> pg_dump (or pg_dumpall) of a database with certain characters in it. I am
> not sure exactly which characters they are, but they did not cause a problem
> in Postgres 8.0, because some of the databases that I cannot backup were
> backed up from 8.0 and restored into 8.1 (there are also problems with data
> entered directly into Postgres 8.1).
Could it be that the client encoding changed from restore to backup?
Which encoding is the backend using? Which one the client?
(to see the backend encoding (it's fixed once you build the DB), just
psql the database and issue \l (list databases). To show/set the client
encoding do "SHOW client_encoding" or "SET client_encoding TO ..."
Or just use \encoding if you are using psql).
PostgreSQL tries to translate back and forth between encodings, but
alas, you can't translate every (utf8 encoded) UNICODE to latin1, for
In response to
pgsql-bugs by date
|Next:||From: zhu||Date: 2006-03-29 10:20:53|
|Subject: BUG #2363: password authentication failed|
|Previous:||From: Jim C. Nasby||Date: 2006-03-27 15:01:47|
|Subject: Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]|