On Wed, Jan 17, 2024 at 2:31 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> Agreed, I think the patch as it stands now where it replaces case insensitive,
> while keeping the original casing, is the best path forward. The issue exist
> in 16 as well so I propose a backpatch to there.
I like that approach, too. I could go either way on back-patching. It
doesn't seem important, but it probably won't break anything, either.
--
Robert Haas
EDB: http://www.enterprisedb.com