| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fixing tsearch locale support |
| Date: | 2024-12-12 18:14:21 |
| Message-ID: | c7835d44c9388b2776ec6ca48d54daffc872377a.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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):
If we do that, then it would be fine to use isdigit/isspace.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-12-12 18:16:39 | TransactionXmin != MyProc->xmin |
| Previous Message | Masahiko Sawada | 2024-12-12 18:08:06 | Re: UUID v7 |