BUG #15516: Identifier not quoted with uppercase letter (spanish Ñ) doesn't get transformed to lowercase (ñ)

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: fcaa(at)tragsa(dot)es
Subject: BUG #15516: Identifier not quoted with uppercase letter (spanish Ñ) doesn't get transformed to lowercase (ñ)
Date: 2018-11-22 16:27:53
Message-ID: 15516-dbfc06804f76790a@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: 15516
Logged by: Paco Calvo
Email address: fcaa(at)tragsa(dot)es
PostgreSQL version: 9.5.15
Operating system: MS Windows Server 2012 R2
Description:

Hi list,

When using an identifier not quoted which includes an uppercase letter
(Spanish Ñ, Unicode U+00D1), it doesn't get transformed to lowercase (ñ,
Unicode U+00F1) as expected. For instance, using a database with UTF-8
encoding and both LC_COLLATE and LC_CTYPE as 'Spanish_Spain.1252', the
following sentence which uses 2 identifiers with a Ñ uppercase letter

CREATE TABLE AÑO (CaÑo integer)

creates the table maintaining both Ñ letters as uppercase and forcing to
quote both identifiers as

CREATE TABLE "aÑo" ("caÑo" integer)

instead of all lowercase and no quoting as expected

CREATE TABLE año (caño integer)

This quirk in lowercasing identifiers forces to use a different, quoted
identifier or manually change afterwards every identifier.

NB: Reproduced also with PostgreSQL 9.6.9 on MS Windows Server 2012 R2 and
PostgreSQL 11.1 on MS Windows Server 2008 R2. Waiting to test it under Linux
and MacOS.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-11-22 16:42:14 Re: New sessions on a database to be dropped consume 100% cpu
Previous Message Feike Steenbergen 2018-11-22 15:50:54 New sessions on a database to be dropped consume 100% cpu