Skip site navigation (1) Skip section navigation (2)

BUG #4098: Encoding problems

From: "Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4098: Encoding problems
Date: 2008-04-07 16:16:12
Message-ID: 200804071616.m37GGCa6023752@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      4098
Logged by:          Jan-Peter Seifert
Email address:      Jan-Peter(dot)Seifert(at)gmx(dot)de
PostgreSQL version: 8.2
Operating system:   Windows xp
Description:        Encoding problems
Details: 

The encoding of the source db/server is LATIN1. The data type of the field
is text (The storage mode is extended). It's/was possible to add characters
available in CP1252 but not in LATIN1 like the Euro character (code 80).
When exporting to UTF8 via "pg_dump -o -U postgres -E UTF-8 ..." (iconv?) it
just adds the character with the code "C2" before the Euro character in the
dump. When importing the dump to a server/db with CP1252 it just throws an
error because of the inconvertible character (0xc280) and seems to stop with
no further error messages (at least the whole table in question is empty
although filled in the source db). It wasn't an issue before the
restrictions were put in place, because the C locale is insufficient.

Responses

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2008-04-07 17:46:29
Subject: Re: BUG #4098: Encoding problems
Previous:From: J6MDate: 2008-04-07 15:56:17
Subject: Re: BUG #4096: PG 8.3.1. confused about remaining disk space

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group