From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <pchampion@vmware.com>
cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>,
        "sfrost@snowman.net" <sfrost@snowman.net>
Subject: Re: Fixing cache pollution in the Kerberos test suite
In-reply-to: <6933ad07afc4c8325059eb9c40ec213fa40adf35.camel@vmware.com>
References: <1fcb175bafef6560f47a8c31229fa7c938486b8d.camel@vmware.com>
 <20210125183645.GF27507@tamriel.snowman.net>
 <1894698.1611600541@sss.pgh.pa.us>
 <0c0cbc9b9a7a1bcd6e78e5eddf706ddeba0293da.camel@vmware.com>
 <1895343.1611601474@sss.pgh.pa.us>
 <6933ad07afc4c8325059eb9c40ec213fa40adf35.camel@vmware.com>
Comments: In-reply-to Jacob Champion <pchampion@vmware.com>
	message dated "Mon, 25 Jan 2021 19:31:16 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1900390.1611604486.1@sss.pgh.pa.us>
Date: Mon, 25 Jan 2021 14:54:46 -0500
Message-ID: <1900391.1611604486@sss.pgh.pa.us>
Precedence: bulk

Jacob Champion <pchampion@vmware.com> writes:
> On Mon, 2021-01-25 at 14:04 -0500, Tom Lane wrote:
>> 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 :)

I tweaked this to make it look a bit more like the rest of the script,
and pushed it.  Thanks!

			regards, tom lane