Re: check_strxfrm_bug() - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: check_strxfrm_bug()
Date
Msg-id CA+hUKGL83_xv4ak0bYz2eBu1C0ADVf5497SSAg5VJXDx+qwagw@mail.gmail.com
Whole thread Raw
In response to Re: check_strxfrm_bug()  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: check_strxfrm_bug()
List 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...



pgsql-hackers by date:

Previous
From: Rémi Lapeyre
Date:
Subject: [PATCH] Add support for postgres:// URIs to PGDATABASE environment variable
Next
From: David Rowley
Date:
Subject: Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?