Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 6AD562E004F for ; Thu, 29 Nov 2007 18:14:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 90623-07 for ; Thu, 29 Nov 2007 18:14:17 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D1EEE2E011D for ; Thu, 29 Nov 2007 18:14:20 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lATMEIqC019841; Thu, 29 Nov 2007 17:14:18 -0500 (EST) To: "Peter Koczan" cc: "pgsql-admin@postgresql.org" Subject: Re: Converting from SQL_ASCII to UTF8 In-reply-to: <4544e0330711291337y4c875320r36414692972296a4@mail.gmail.com> References: <4544e0330711291337y4c875320r36414692972296a4@mail.gmail.com> Comments: In-reply-to "Peter Koczan" message dated "Thu, 29 Nov 2007 15:37:06 -0600" Date: Thu, 29 Nov 2007 17:14:18 -0500 Message-ID: <19840.1196374458@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/248 X-Sequence-Number: 27491 "Peter Koczan" writes: > I have some UTF-8 data in my databases, and it's causing dump/restore > to fail. Specifically, I'm seeing messages like: > pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence > for encoding "UTF8": 0xe14c65 This is, in fact, not UTF8, no matter how much you'd like to think so. It might possibly be LATIN1 or some other single-byte encoding. What you're going to need to do is figure out what you really have and convert it all to a common encoding. One of the disadvantages of SQL_ASCII mode is that it will let you wind up with a mishmash of different encodings in your DB :-( regards, tom lane