From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gary Stainburn <gary.stainburn@ringways.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: yum update now gives me UNICODE errors
Date: Thu, 24 Aug 2006 10:41:04 -0400
Message-ID: <4645.1156430464@sss.pgh.pa.us> (raw)
In-Reply-To: <200608241343.00499.gary.stainburn@ringways.co.uk>
References: <200608241343.00499.gary.stainburn@ringways.co.uk>
Gary Stainburn <gary.stainburn@ringways.co.uk> writes:
> ERROR: invalid byte sequence for encoding "UNICODE": 0xa3
> The problem is the £ (pound sterling) sign, but I never had any problems prior
> to the update.
Postgres didn't use to be quite as picky about the encoding as it is
now. What you are sending it is not UTF-8, and you can no longer
get away with pretending that it is. It looks like you're probably
using Latin1 (ISO 8859-1) or something related. Assuming that that's
what's really in your database, what I'd do is
- dump the database
- edit the SET client_encoding command at the head of the dump
file to say the correct encoding
- initdb in the correct locale (one using your encoding,
not utf8)
- reload data
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gary.stainburn@ringways.co.uk
Subject: Re: yum update now gives me UNICODE errors
In-Reply-To: <4645.1156430464@sss.pgh.pa.us>
References: <200608241343.00499.gary.stainburn@ringways.co.uk> <4645.1156430464@sss.pgh.pa.us>
* 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