Re: [18] Unintentional behavior change in commit e9931bfb75 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [18] Unintentional behavior change in commit e9931bfb75
Date
Msg-id 1747800.1733207567@sss.pgh.pa.us
Whole thread Raw
In response to Re: [18] Unintentional behavior change in commit e9931bfb75  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Jeff Davis <pgsql@j-davis.com> writes:
> On Mon, 2024-12-02 at 17:25 -0500, Tom Lane wrote:
>> Well, also for compatibility with our SQL parser's understanding
>> of identifier lowercasing.

> But why only for single-byte encodings? And why not for ICU?

I think the not-for-utf8 exclusion was mostly because that was
how it was before, which was probably mostly historical accident.
(I do vaguely recall that there was discussion on the point, but
I'm too tired to go look in the archives for it.)

As for ICU, that didn't exist back then, and I'm not going to
defend whether it was a good idea for that code path to fail
to reproduce this behavior.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: [18] Unintentional behavior change in commit e9931bfb75
Next
From: jian he
Date:
Subject: Re: speedup ALTER TABLE ADD CHECK CONSTRAINT.