Home > mailing lists

Character encoding problems and dump import - Mailing list pgsql-admin

From
Subject	Character encoding problems and dump import
Date	March 20, 2006 19:21:38
Msg-id	20060320202135.86240.qmail@web50302.mail.yahoo.com Whole thread Raw
Responses	Re: Character encoding problems and dump import (Ivo Rossacher <rossacher@bluewin.ch>) Re: Character encoding problems and dump import (John DeSoi <desoi@pgedit.com>)
List	pgsql-admin

Tree view

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:

=> \encoding
UNICODE

Characters that cause problems during the import are things like:
é and other characters from the Extended ASCII table (c.f. bottom of http://www.lookuptables.com/ )
Also:
'ÇÑ±ÛÀÌ Á¦´ë·Î µÇ´ÂÁö ½ÇÇè... ¿©±â¿¡´Â ¾Æ¹« ¸µÅ©µµ ¾ø½À´Ï´Ù.±×³É ÀÌ ³»¿ë¹Û¿¡ ¾ø½À´Ï´Ù.'


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
intosomething else. 

Thanks,
Otis

pgsql-admin by date:

From: "Magnus Hagander"
Date: 20 March 2006, 17:51:57
Subject: Re: Starting in a Windows administrative account

From: "Mr. Dan"
Date: 20 March 2006, 20:19:36
Subject: hiding the postgres password - v8.1.0

Character encoding problems and dump import - Mailing list pgsql-admin

Previous

Next