BUG #14170: error message in case LOCALE de_DE.UTF8 is used in combination with CLIENT_ENCODING=LATIN1

From: dag-hammerich(at)gmx(dot)de
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14170: error message in case LOCALE de_DE.UTF8 is used in combination with CLIENT_ENCODING=LATIN1
Date: 2016-06-01 12:06:22
Message-ID: 20160601120622.30384.57513@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14170
Logged by: Dag Hammerich
Email address: dag-hammerich(at)gmx(dot)de
PostgreSQL version: 9.4.8
Operating system: Ubuntu 14.04 LTS
Description:

I think postgres cannot correctly "translate" its error message for this
special situation because for LOCALE "de_DE" it seems that "double
quotsation marks left" are used that are not defined in (for example)
LATIN1.

To reproduce it the following could be done:

1. create new DB-cluster by with corresponding locale:
initdb --locale=de_DE.UTF8

2. set CLIENT_ENCODING or environment variable PGCLIENTENCODING to LATIN1

3. produce any error that forces postgres to react with an error message,
e.g. by a syntax error in SQL or dropping a DB that doesn't exist using this
command line:
dropdb xyz

>>> this will result in:
ERROR: character with byte sequence 0xe2 0x80 0x9e in encoding "UTF8" has no
equivalent in encoding "LATIN1"

The mentioned byte sequence are „German double quots left”.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Meskes 2016-06-01 13:43:00 Re: BUG #14167: ecpg parser cann't ignore code in #ifdef ?
Previous Message Vladimir Sitnikov 2016-06-01 11:23:29 Re: Re: [BUGS] BUG #14166: JDBC driver won't parse error message from DB server in German