Обсуждение: encoding error in new Postgres version
Good morning
We recently (last month) upgraded from postgres 8.2 to 8.3.
We run linux redhat on our production servers, although a couple
Of our developers run Windows XP 32 bit. They restore a pg_dump
Copy of our production database onto their local machine.
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
I’ve had him change CLIIENT_ENCODING to UTF-8, then to WIN1252 all to no avail.
I also tried running the pgdump file through the ICONV program on the linux side before
Porting it over.
We don’t have this problem in any of our linux environments.
I’ve attached the developer’s postgresql.conf file for your reference. Any help appreciated.
Thank you,
Mark Steben│Database Administrator
@utoRevenue®-"Join the Revenue-tion"
95 Ashley Ave., West Springfield, Ma
413-243-4800 x1512 (Phone) │ 413.732-1824 (Fax)
@utoRevenue is a registered trademark and a division of Dominion Enterprises
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