On Sat, Jul 17, 2021 at 9:37 PM Tom Lane wrote:
>
> Bharath Rupireddy writes:
> > On Thu, Jul 15, 2021 at 3:48 AM Tom Lane wrote:
> >> More generally, though, I am not sure that I believe the premise of
> >> this patch. AFAICS it's assuming that forcing debug_discard_caches
> >> off guarantees
Bharath Rupireddy writes:
> On Thu, Jul 15, 2021 at 3:48 AM Tom Lane wrote:
>> More generally, though, I am not sure that I believe the premise of
>> this patch. AFAICS it's assuming that forcing debug_discard_caches
>> off guarantees zero cache flushes, which it does not.
> Can the setting deb
On Thu, Jul 15, 2021 at 3:48 AM Tom Lane wrote:
>
> Bharath Rupireddy writes:
> > While working on [1], I got to know that there is a new GUC
> > debug_invalidate_system_caches_always that has been introduced in v14.
> > It can be used to switch off cache invalidation in
> > CLOBBER_CACHE_ALWAYS
On Mon, May 10, 2021 at 6:03 PM Bharath Rupireddy
wrote:
>
> Hi,
>
> While working on [1], I got to know that there is a new GUC
> debug_invalidate_system_caches_always that has been introduced in v14.
> It can be used to switch off cache invalidation in
> CLOBBER_CACHE_ALWAYS builds which makes c
Bharath Rupireddy writes:
> While working on [1], I got to know that there is a new GUC
> debug_invalidate_system_caches_always that has been introduced in v14.
> It can be used to switch off cache invalidation in
> CLOBBER_CACHE_ALWAYS builds which makes cache sensitive tests stable.
> Using this
