Re: multibyte-character aware support for function "downcase_truncate_identifier()"

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Nov 21, 2010 at 6:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> spec compliance aside, we know from bitter experience that we cannot use
>> a definition that lets the Turkish locale fool with the mapping of i/I.
>> I suspect that locale-dependent mappings of any other characters are
>> just as bad, we simply haven't had enough users burnt by such cases to
>> have an institutional memory of it. But for example do you really think
>> it's a good idea if pg_dump and reload into a DB with a different locale
>> results in changing the normalized form of SQL identifiers?

> No, especially if it results in queries that used to work breaking,
> which it well could. But I'm not sure where to go with it from there,
> beyond throwing up my hands.

Well, that's why there's been no movement on this since 2004 :-(. The
amount of work needed for a better solution seems far out of proportion
to the benefits.

regards, tom lane