On Mon, 2024-12-02 at 11:57 +0100, Peter Eisentraut wrote: > t_isdigit() and t_isspace() are just used to parse various > configuration > and data files, and surely we don't need support for encoding- > dependent > multibyte support for parsing ASCII digits and ASCII spaces. > ... So these can > be > replaced by the normal isdigit() and isspace().
That would still call libc, and still depend on LC_CTYPE. Should we use pure ASCII variants? There was also some discussion about forcing LC_COLLATE and LC_CTYPE to C, now that the default collation doesn't depend on them any more (cf. option 1): https://www.postgresql.org/message-id/ca+hukgl82jg2pdgfqtwwg+_51tq--6m9xna3rtt7ub+s3pm...@mail.gmail.com If we do that, then it would be fine to use isdigit/isspace. Regards, Jeff Davis
