Skip site navigation (1) Skip section navigation (2)

Re: encoding error in new Postgres version

From: Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>
To: Mark Steben <msteben(at)autorevenue(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: encoding error in new Postgres version
Date: 2010-02-02 23:07:48
Message-ID: 4B68B044.5040804@gmx.de (view raw or flat)
Thread:
Lists: pgsql-admin
Hello,

nobody did answer so far it seems ...

> In 8.2 they had no problem.  In 8.3, however they now get the following
> error
> 
> On several tables: 

>    pg_restore: [archiver (db)] COPY failed: ERROR:  character 0xe28899
> of encoding "UTF8" has no equivalent in "WIN1252"
> CONTEXT:  COPY emails, line 3923

8.3 is more strict about encodings and locales. What encoding do source
(UTF8?) and target (WIN1252?) data base use? What are the locales (use
binary program pg_controldata on the cluster directories)?

Dump the problematic tables directly in plain text format and go to the
line which causes the error (e.g. line 3923 of data) and check for
characters not defined in WIN1252. If you use an ASCII editor you'll
most likely see a character that is used for 'undefined' characters - a
hollow square, a question mark etc.
http://en.wikipedia.org/wiki/Windows-1252
In your example it seems to be this character:
http://decodeunicode.org/en/u+2219/properties
Clean in it up in the source table if you've identified any problematic
character.

Good luck,

Peter





In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2010-02-02 23:17:07
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Previous:From: Wang, Mary YDate: 2010-02-02 22:29:08
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group