Re: check_strxfrm_bug()
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-16T20:00:22Z
Lists: pgsql-hackers
On Sun, Dec 18, 2022 at 10:27 AM Thomas Munro <thomas.munro@gmail.com> wrote: > With my garbage collector hat on, that made me wonder if there was > some more potential cleanup here: could we require locale_t yet? The > last straggler systems on our target OS list to add the POSIX locale_t > stuff were Solaris 11.4 (2018) and OpenBSD 6.2 (2018). Apparently > it's still too soon: we have two EOL'd OSes in the farm that are older > than that. But here's an interesting fact about wrasse, assuming its > host is gcc211: it looks like it can't even apply further OS updates > because the hardware[1] is so old that Solaris doesn't support it > anymore[2]. For the record, now the OpenBSD machines have been upgraded, so now "wrasse" is the last relevant computer on earth with no POSIX locale_t. Unfortunately there is no reason to think it's going to go away soon, so I'm just noting this fact here as a reminder for when it eventually does...
Commits
-
Don't expose Windows' mbstowcs_l() and wcstombs_l().
- 4e9fa6d56b3e 17.0 landed
-
All supported systems have locale_t.
- 8d9a9f034e92 17.0 landed
-
Remove obsolete defense against strxfrm() bugs.
- 7d3d72b55edd 16.0 landed