Re: Why is citext/regress failing on hamerkop?

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Oleg Tselebrovskiy <o(dot)tselebrovskiy(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is citext/regress failing on hamerkop?
Date: 2024-08-02 14:11:10
Message-ID: 29C47E3C-4519-4A89-A748-0AEBB810BF0A@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Aug 1, 2024, at 18:54, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:

> Done (e52a44b8, 91f498fd).
>
> Any elucidation on how and why Windows machines have started using
> UTF-8 would be welcome.

Haven’t been following this thread, but this post reminded me of an issue I saw with locales on Windows[1]. Could it be that the introduction of Universal CRT[2] in Windows 10 has improved UTF-8 support?

Bit of a wild guess, but I assume worth bringing up at least.

D

[1]: https://github.com/shogo82148/actions-setup-perl/issues/1713
[2]: https://learn.microsoft.com/en-us/cpp/porting/upgrade-your-code-to-the-universal-crt?view=msvc-170

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-08-02 14:14:52 Re: can we mark upper/lower/textlike functions leakproof?
Previous Message Joe Conway 2024-08-02 13:58:37 Re: can we mark upper/lower/textlike functions leakproof?