Re: Fixing cache pollution in the Kerberos test suite
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Jacob Champion <pchampion@vmware.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-01-25T18:36:46Z
Lists: pgsql-hackers
Greetings, * Jacob Champion (pchampion@vmware.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
Commits
-
Don't clobber the calling user's credentials cache in Kerberos test.
- b8894a3661d4 11.11 landed
- 881933f19422 14.0 landed
- 820aa9ef4c35 12.6 landed
- 366d302d14f7 13.2 landed