Re: Multi-byte character case-folding

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Multi-byte character case-folding
Date: 2020-07-06 22:46:23
Message-ID: 20200706224623.GA20132@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2020-Jul-06, Tom Lane wrote:

> More generally, I'd be mighty hesitant to change this behavior after
> it's stood for so many years. I suspect more people would complain
> that we broke their application than would be happy about it.
> Having said that, we are already relying on towlower() in places,
> and could do similarly here if we didn't care about the above issues.

I think the fact that identifiers fail to follow language-specific case
folding rules is more a known gotcha than a desired property, but on
principle I tend to agree that Turkish people would not be happy about
the prospect of us changing the downcasing rule in a major release -- it
would mean having to edit any affected application code as part of a
pg_upgrade process, which is not great.

Now you could say that this can be fixed by adding a GUC that preserves
the old behavior, but generally we don't like that too much.

The counter argument is that there are more future users than there are
current users.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2020-07-07 00:16:50 Re: Binary support for pgoutput plugin
Previous Message Soumyadeep Chakraborty 2020-07-06 22:45:23 Re: posgres 12 bug (partitioned table)