Horton
Menu

Re: Why is citext/regress failing on hamerkop?

Alexander Lakhin <exclusion@gmail.com>

View thread
From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-12T11:00:00Z
Lists: pgsql-hackers 
Hello Tom,

12.05.2024 08:34, Tom Lane wrote:
> BTW, I've also been wondering why hamerkop has been failing
> isolation-check in the 12 and 13 branches for the last six months
> or so.  It is surely unrelated to this issue, and it looks like
> it must be due to some platform change rather than anything we
> committed at the time.
>
> I'm not planning on looking into that question myself, but really
> somebody ought to.  Or is Windows just as dead as AIX, in terms of
> anybody being willing to put effort into supporting it?

I've reproduced the failure locally with GSS enabled, so I'll try to
figure out what's going on here in the next few days.

Best regards,
Alexander

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