X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 23D2E9DCA5E for ; Mon, 20 Mar 2006 16:21:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68389-01 for ; Mon, 20 Mar 2006 16:21:38 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web50302.mail.yahoo.com (web50302.mail.yahoo.com [206.190.38.56]) by postgresql.org (Postfix) with SMTP id F16FC9DD4FB for ; Mon, 20 Mar 2006 16:21:34 -0400 (AST) Received: (qmail 86246 invoked by uid 60001); 20 Mar 2006 20:21:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xi09CMBCoO2ePQgEdxYf/XzKiMbyePSd1XT97bPLNPXXaXtdCH5eo7HJM0q5YDqR39+hYBkZ3/M2oSY/33wxadH3Wyv3FLfOnEw/konv6oDI7TevidwjZjDsINFXqG2Xajzfa5+3/5gCNvyQjKbP9Rj+ZwiTtaPnS0SAWofj4sM= ; Message-ID: <20060320202135.86240.qmail@web50302.mail.yahoo.com> Date: Mon, 20 Mar 2006 12:21:35 -0800 (PST) From: Subject: Character encoding problems and dump import To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=2.616 required=5 tests=[AWL=-0.220, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_WHOIS=0.879, FORGED_YAHOO_RCVD=0.928, NO_REAL_NAME=0.55] X-Spam-Score: 2.616 X-Spam-Level: ** X-Archive-Number: 200603/180 X-Sequence-Number: 20937 Hello, I have a dump (non-binary, if it matters) of a DB that has some characters = in it that my DB doesn't want to take. I'm using PG 8.0.3 and it was created with Unicode support: =3D> \encoding UNICODE Characters that cause problems during the import are things like: =C3=A9 and other characters from the Extended ASCII table (c.f. bottom of h= ttp://www.lookuptables.com/ ) Also: '=C3=87=C3=91=C2=B1=C3=9B=C3=80=C3=8C =C3=81=C2=A6=C2=B4=C3=AB=C2=B7=C3=8E = =C2=B5=C3=87=C2=B4=C3=82=C3=81=C3=B6 =C2=BD=C3=87=C3=87=C3=A8... =C2=BF=C2= =A9=C2=B1=C3=A2=C2=BF=C2=A1=C2=B4=C3=82 =C2=BE=C3=86=C2=B9=C2=AB =C2=B8=C2= =B5=C3=85=C2=A9=C2=B5=C2=B5 =C2=BE=C3=B8=C2=BD=C3=80=C2=B4=C3=8F=C2=B4=C3= =99.=C2=B1=C3=97=C2=B3=C3=89 =C3=80=C3=8C =C2=B3=C2=BB=C2=BF=C3=AB=C2=B9=C3= =9B=C2=BF=C2=A1 =C2=BE=C3=B8=C2=BD=C3=80=C2=B4=C3=8F=C2=B4=C3=99.' The errors I get on import are of this type: ERROR: invalid byte sequence for encoding "UNICODE": 0xdb20 The data may not be the cleanest, and I have limited control over that. But I am wondering if there is any way I can import this data, even if that= means converting some of the characters into something else. Thanks, Otis