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

From Tom Lane
Subject Re: Fixing cache pollution in the Kerberos test suite
Date
Msg-id 1895343.1611601474@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fixing cache pollution in the Kerberos test suite  (Jacob Champion <pchampion@vmware.com>)
Responses Re: Fixing cache pollution in the Kerberos test suite  (Jacob Champion <pchampion@vmware.com>)
Re: Fixing cache pollution in the Kerberos test suite  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Jacob Champion <pchampion@vmware.com> writes:
> On Mon, 2021-01-25 at 13:49 -0500, Tom Lane wrote:
>> Yeah, changing global state is just awful.  However, I don't
>> actually see any change here (RHEL8):

> Interesting. I'm running Ubuntu 20.04:

Hmm.  I'll poke harder.

>> 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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Fixing cache pollution in the Kerberos test suite
Next
From: Fujii Masao
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit