pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
yum update now gives me UNICODE errors
2+ messages / 2 participants
[nested] [flat]

* yum update now gives me UNICODE errors
@ 2006-08-24 12:43  Gary Stainburn <gary.stainburn@ringways.co.uk>
  0 siblings, 1 reply; 2+ messages in thread

From: Gary Stainburn @ 2006-08-24 12:43 UTC (permalink / raw)
  To: pgsql-admin

Hi folks.

Yesterday I ran a 'yum update' which included upgrading to 8.0.8.

Now when I run a SQL script I get the following errors:

insert into orders (or_supp, or_date, or_received, or_no, or_state, 
or_comments) values 	-- 74
	(4, '2004-02-13', '2004-02-13', 121604,'I','Sony Vaio FR395EP @ £789\nCarry 
Case');
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.

Can anyone tell me what has changed, and how I can change it back.

Thanks
-- 
Gary Stainburn
 
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000     



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: yum update now gives me UNICODE errors
@ 2006-08-24 14:41  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Gary Stainburn <gary.stainburn@ringways.co.uk>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2006-08-24 14:41 UTC (permalink / raw)
  To: Gary Stainburn <gary.stainburn@ringways.co.uk>; +Cc: pgsql-admin

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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2006-08-24 14:41 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-08-24 12:43 yum update now gives me UNICODE errors Gary Stainburn <gary.stainburn@ringways.co.uk>
2006-08-24 14:41 ` Tom Lane <tgl@sss.pgh.pa.us>

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