Horton
Menu

Re: Why is citext/regress failing on hamerkop?

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, buildfarm@sraoss.co.jp
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-12T16:20:48Z
Lists: pgsql-hackers 
On 2024-05-12 Su 08:26, Andrew Dunstan wrote:
>
>
> On 2024-05-12 Su 01: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.
>
>
> Possibly. It looks like this might be the issue:
>
> +Connection 2 failed: could not initiate GSSAPI security context: Unspecified GSS failure.  Minor code may provide more information: Credential cache is empty
> +FATAL:  sorry, too many clients already
>
>
> There are several questions here, including:
>
> 1. why isn't it failing on later branches?
> 2. why isn't it failing on drongo (which has more modern compiler and OS)?
>
> I think we'll need the help of the animal owner to dig into the issue.


Aha! drongo doesn't have GSSAPI enabled. Will work on that.


cheers


andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

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