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

Re: LC_MESSAGES = 'de_AT' screws restoring from dump.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Erwin Brandstetter <a9006241(at)unet(dot)univie(dot)ac(dot)at>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: LC_MESSAGES = 'de_AT' screws restoring from dump.
Date: 2004-06-08 16:40:40
Message-ID: 2894.1086712840@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Erwin Brandstetter <a9006241(at)unet(dot)univie(dot)ac(dot)at> writes:
> # While running with:
> lc_messages = 'de_AT'
> encoding = UNICODE

> psql:./e_schema.sql:157: FEHLER:  could not convert UTF-8 character 
> 0x00fc to ISO8859-1
> psql:./e_schema.sql:159: FEHLER:  Relation naehe existiert nicht

> There seems to be something wrong with German error messages?

I suspect that de_AT on your machine implies a character set encoding
other than Unicode (likely 8859-something).  So strerror() returns
a message that is in 8859-something, but the backend assumes that all
strings inside it are in Unicode, and tries to convert based on that
assumption.  You need to use a locale setting that conforms to the
database encoding you've selected.  It might be called de_AT.utf8
or some such.

It's a real pain in the neck that Postgres can't detect locale settings
that are incompatible with the database encoding.  I don't know any
portable way to find that out, though.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Naomi WalkerDate: 2004-06-08 17:28:02
Subject: Re: out of memory error
Previous:From: Erwin BrandstetterDate: 2004-06-08 16:20:10
Subject: LC_MESSAGES = 'de_AT' screws restoring from dump.

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