Re: Why is citext/regress failing on hamerkop?

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Oleg Tselebrovskiy <o.tselebrovskiy@postgrespro.ru>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2024-08-01T22:54:02Z

Lists: pgsql-hackers

On Fri, Aug 2, 2024 at 1:37 AM Oleg Tselebrovskiy
<o.tselebrovskiy@postgrespro.ru> wrote:
> I would appreciate if you would backpatch this change to 15 and 16
> branches.

Done (e52a44b8, 91f498fd).

Any elucidation on how and why Windows machines have started using
UTF-8 would be welcome.

Commits

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

Small refactoring around ExecCreateTableAs().
- 7926a9a80f6d 18.0 cited
Skip citext_utf8 test on Windows.
- e52a44b8a4c1 15.8 landed
- 91f498fdec14 16.4 landed
- cff4e5a36bfe 17.0 landed
Fix lost Windows socket EOF events.
- ba9fcac7209d 12.20 landed
- 3554d841d216 13.16 landed
- 894b497ac91d 14.13 landed
- 5546a834cc6f 15.8 landed
- a622095bcc4d 16.4 landed
- 3c1c82d4066e 17.0 landed
- a8458f508a7a 18.0 landed
Enable routine running of citext's UTF8-specific test cases.
- c2e8bd27519f 15.0 cited
Drops in the CreateProcess calls for Win32 (essentially wrapping up the
- 4cdf51e64627 8.0.0 cited