Re: Fixing cache pollution in the Kerberos test suite

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <pchampion(at)vmware(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net>
Subject: Re: Fixing cache pollution in the Kerberos test suite
Date: 2021-01-25 19:54:46
Message-ID: 1900391.1611604486@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <pchampion(at)vmware(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-01-25 19:58:16 Re: Fixing cache pollution in the Kerberos test suite
Previous Message Jacob Champion 2021-01-25 19:50:47 Re: Fixing cache pollution in the Kerberos test suite