Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id D01D4633A06 for ; Tue, 2 Feb 2010 19:08:16 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 16456-07-3 for ; Tue, 2 Feb 2010 23:07:51 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mail.postgresql.org (Postfix) with SMTP id C45356340AD for ; Tue, 2 Feb 2010 19:07:51 -0400 (AST) Received: (qmail invoked by alias); 02 Feb 2010 23:07:49 -0000 Received: from unknown (EHLO [192.168.178.22]) [188.194.161.72] by mail.gmx.net (mp067) with SMTP; 03 Feb 2010 00:07:49 +0100 X-Authenticated: #955937 X-Provags-ID: V01U2FsdGVkX18s/2U6qHQsa31rpDZSaGab8ZbSyoVh5jRAZ+pFkk ASY+EjHJ4Iw1O7 Message-ID: <4B68B044.5040804@gmx.de> Date: Wed, 03 Feb 2010 00:07:48 +0100 From: Jan-Peter Seifert User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Mark Steben CC: pgsql-admin@postgresql.org Subject: Re: encoding error in new Postgres version References: <20091215160534.5F983632C55@mail.postgresql.org> In-Reply-To: <20091215160534.5F983632C55@mail.postgresql.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.56999999999999995 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.392 tagged_above=-10 required=5 tests=AWL=-1.207, BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201002/30 X-Sequence-Number: 33633 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