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 EB6C39DD581 for ; Tue, 21 Mar 2006 10:46:45 -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 88029-08 for ; Tue, 21 Mar 2006 10:46:49 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web50313.mail.yahoo.com (web50313.mail.yahoo.com [206.190.39.215]) by postgresql.org (Postfix) with SMTP id CCD189DCA30 for ; Tue, 21 Mar 2006 10:46:42 -0400 (AST) Received: (qmail 71822 invoked by uid 60001); 21 Mar 2006 14:46:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JbKhP7rPH+Gnhf9O+zp7jaj/3yefnnTaO3IAlha1LfVxghiV3NRAiAhbNdaZd9VB2vqpOTuhIFG+F3CErLDmGlXd8meeyTeRfwnUIY4mWgIlkqNSWJiK2OItDvEiuXuopRNZWdpHKVpQKkW9P1MYOKbcokuyq4FfySmGPwX95l0= ; Message-ID: <20060321144646.71820.qmail@web50313.mail.yahoo.com> Date: Tue, 21 Mar 2006 06:46:46 -0800 (PST) From: Subject: Re: Character encoding problems and dump import To: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/189 X-Sequence-Number: 20946 Thanks John and Ivo for help. It turned out that I had to manually SET CLIENT_ENCODING TO 'LATIN1' before processing the dump (which didn't have this specified). This fixed the problem. I thought a DB set to UNICODE char encoding (server_encoding) would process the Extended ASCII characters, but it didn't... not sure why. Otis ----- Original Message ---- From: John DeSoi To: ogjunk-pgjedan@yahoo.com Cc: pgsql-admin@postgresql.org Sent: Tuesday, March 21, 2006 12:31:16 AM Subject: Re: [ADMIN] Character encoding problems and dump import On Mar 20, 2006, at 3:21 PM, wrote: > 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. inconv might be able to help you fix encoding problems http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org