Re: [18] Unintentional behavior change in commit e9931bfb75
От
Tom Lane
Тема
Re: [18] Unintentional behavior change in commit e9931bfb75
Дата
Msg-id
1747800.1733207567@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
[18] Unintentional behavior change in commit e9931bfb75 Jeff Davis <pgsql@j-davis.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Tom Lane <tgl@sss.pgh.pa.us>
Re: [18] Unintentional behavior change in commit e9931bfb75 Jeff Davis <pgsql@j-davis.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Tom Lane <tgl@sss.pgh.pa.us>
Re: [18] Unintentional behavior change in commit e9931bfb75 Noah Misch <noah@leadboat.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Jeff Davis <pgsql@j-davis.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Noah Misch <noah@leadboat.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Jeff Davis <pgsql@j-davis.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Noah Misch <noah@leadboat.com>
Re: [18] Unintentional behavior change in commit e9931bfb75 Peter Eisentraut <peter@eisentraut.org>
Re: [18] Unintentional behavior change in commit e9931bfb75 Tom Lane <tgl@sss.pgh.pa.us>
Re: [18] Unintentional behavior change in commit e9931bfb75 Jeff Davis <pgsql@j-davis.com>
Jeff Davis 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 по дате отправления
От: Jeff Davis
Дата: