Re: Fixing cache pollution in the Kerberos test suite - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Fixing cache pollution in the Kerberos test suite
Date
Msg-id 6933ad07afc4c8325059eb9c40ec213fa40adf35.camel@vmware.com
Whole thread Raw
In response to Re: Fixing cache pollution in the Kerberos test suite  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing cache pollution in the Kerberos test suite  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 2021-01-25 at 14:04 -0500, Tom Lane wrote:
> Jacob Champion <pchampion@vmware.com> writes:
> > On Mon, 2021-01-25 at 13:49 -0500, Tom Lane wrote:
> > > Also, why are you only setting the ENV variable within narrow parts
> > > of the test script?  I'd be inclined to enforce it throughout.
> > I considered it and decided I didn't want to pollute the server's
> > environment with it, since the server shouldn't need the client cache.
> 
> True, but if it did try to access the cache, accessing the user's
> normal cache would be strictly worse than accessing the test cache.

That's fair. Attached is a v2 that just sets KRB5CCNAME globally. Makes
for a much smaller patch :)

--Jacob

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Key management with tests
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: [UNVERIFIED SENDER] Re: Minimal logical decoding on standbys