From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Jacob Champion <pchampion(at)vmware(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Fixing cache pollution in the Kerberos test suite |
Date: | 2021-01-25 18:36:46 |
Message-ID: | 20210125183645.GF27507@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Jacob Champion (pchampion(at)vmware(dot)com) wrote:
> I was running tests with a GSS-enabled stack, and ran into some very
> long psql timeouts after running the Kerberos test suite. It turns out
> the suite pushes test credentials into the user's global cache, and
> these no-longer-useful credentials persist after the suite has
> finished. (You can see this in action by running the test/kerberos
> suite and then running `klist`.) This leads to long hangs, I assume
> while the GSS implementation tries to contact a KDC that no longer
> exists.
> Attached is a patch that initializes a local credentials cache inside
> tmp_check/krb5cc, and tells psql to use it via the KRB5CCNAME envvar.
> This prevents the global cache pollution. WDYT?
Ah, yeah, that generally seems like a good idea.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-01-25 18:49:01 | Re: Fixing cache pollution in the Kerberos test suite |
Previous Message | Jacob Champion | 2021-01-25 18:33:18 | Fixing cache pollution in the Kerberos test suite |