Re: check_strxfrm_bug()

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: check_strxfrm_bug()
Date: 2023-04-16 20:00:22
Message-ID: CA+hUKGL83_xv4ak0bYz2eBu1C0ADVf5497SSAg5VJXDx+qwagw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 18, 2022 at 10:27 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)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...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-16 21:31:24 Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?
Previous Message Rémi Lapeyre 2023-04-16 18:42:17 [PATCH] Add support for postgres:// URIs to PGDATABASE environment variable