Re: Character encoding problems and dump import

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 <desoi(at)pgedit(dot)com>
To: ogjunk-pgjedan(at)yahoo(dot)com
Cc: pgsql-admin(at)postgresql(dot)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, <ogjunk-pgjedan(at)yahoo(dot)com> <ogjunk-
pgjedan(at)yahoo(dot)com> 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