Re: check_strxfrm_bug()
От | Thomas Munro |
---|---|
Тема | Re: check_strxfrm_bug() |
Дата | |
Msg-id | CA+hUKGJrdk12oxMZgbdQt_Ca7gp_mWEPXzwQ6B97BBv=tfTsXQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: check_strxfrm_bug() ("Jonathan S. Katz" <jkatz@postgresql.org>) |
Ответы |
Re: check_strxfrm_bug()
Re: check_strxfrm_bug() |
Список | pgsql-hackers |
On Wed, Apr 19, 2023 at 2:31 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > To be clear, is the proposal to remove both "check_strxfrm_bug" and > "TRUST_STRXFRM"? > > Given a bunch of folks who have expertise in this area of code all agree > with removing the above as part of the collation cleanups targeted for > v16, I'm inclined to agree. I don't really see the need for an explicit > RMT action, but based on the consensus this seems OK to add as an open item. Thanks all. I went ahead and removed check_strxfrm_bug(). I could write a patch to remove the libc strxfrm support, but since Jeff recently wrote new code in 16 to abstract that stuff, he might prefer to look at it?
В списке pgsql-hackers по дате отправления: