Horton
Menu

Re: Why is citext/regress failing on hamerkop?

David E. Wheeler <david@justatheory.com>

View thread
From: "David E. Wheeler" <david@justatheory.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Oleg Tselebrovskiy <o.tselebrovskiy@postgrespro.ru>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-08-02T14:11:10Z
Lists: pgsql-hackers 
On Aug 1, 2024, at 18:54, Thomas Munro <thomas.munro@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Small refactoring around ExecCreateTableAs().

  2. Skip citext_utf8 test on Windows.

  3. Fix lost Windows socket EOF events.

  4. Enable routine running of citext's UTF8-specific test cases.

  5. Drops in the CreateProcess calls for Win32 (essentially wrapping up the