X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id EC7579FB22B for ; Mon, 7 Aug 2006 23:08:35 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 59290-03 for ; Tue, 8 Aug 2006 02:08:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from stash.illumen.com (unknown [64.207.29.137]) by postgresql.org (Postfix) with ESMTP id C32739FB21F for ; Mon, 7 Aug 2006 23:08:25 -0300 (ADT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6BA8F.87161A79" Subject: Strange UTF8 issue with pg_dump/pg_restore X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 7 Aug 2006 20:08:23 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Strange UTF8 issue with pg_dump/pg_restore Thread-Index: Aca6ifctc6KKIygSSX2NOJRBY3kKAQABLhnw From: "Benjamin Krajmalnik" To: "pgsql admin" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/81 X-Sequence-Number: 22625 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6BA8F.87161A79 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a database whose records are inserted via ODBC. I turned on logging, and the client is explicitly setting the client encoding to UTF. =20 Rows are inserted into the tables. When I do a pg_dump, I do not get any errors. When I try tor restore, I am getting an error regarding an invalid UTF-8 character sequence. Of course, this renders compressed backups useless, since I have no way of manually fixing the file. The process of fixing the file is, of course, painful. =20 Is this a known issue? I am running PG 8.1.4. The problem happened on PG Windows. Tomorrow I will try to see if the problem exists in the FreeBSD compile. If I get it to reproduce, I will be able to send some data dumps, but will need to know who to send it to. =20 Regards, =20 Benjamin =20 =20 ------_=_NextPart_001_01C6BA8F.87161A79 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I have a database whose records are inserted = via=20 ODBC.
I turned on logging, and the client is = explicitly setting=20 the client encoding to UTF.
 
Rows are inserted into the tables.  When I = do a=20 pg_dump, I do not get any errors.  When I try tor restore, I am = getting an=20 error regarding an invalid UTF-8 character sequence.
Of course, this renders compressed backups = useless, since I=20 have no way of manually fixing the file.  The process of fixing the = file=20 is, of course, painful.
 
Is this a known issue?  I am running PG = 8.1.4. =20 The problem happened on PG Windows.
Tomorrow I will try to see if the problem = exists in the=20 FreeBSD compile.  If I get it to reproduce, I will be able to send = some=20 data dumps, but will need to know who to send it to.
 
Regards,
 
Benjamin
 
 
------_=_NextPart_001_01C6BA8F.87161A79--