Re: Why is citext/regress failing on hamerkop?
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-16T01:32:08Z
Lists: pgsql-hackers
On Thu, May 16, 2024 at 10:43 AM Thomas Munro <thomas.munro@gmail.com> wrote: > Any chance you could test this version please Alexander? Sorry, cancel that. v3 is not good. I assume it fixes the GSSAPI thing and is superficially better, but it doesn't handle code that calls twice in a row and ignores the first result (I know that PostgreSQL does that occasionally in a few places), and it's also broken if someone gets recv() = 0 (EOF), and then decides to wait anyway. The only ways I can think of to get full reliable poll()-like semantics is to do that peek every time, OR the complicated patch (per-socket-workspace + intercepting recv etc). So I'm back to v2.
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