Re: Some other CLOBBER_CACHE_ALWAYS culprits

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Some other CLOBBER_CACHE_ALWAYS culprits
Date: 2021-05-14 21:36:51
Message-ID: 20210514213651.GA27122@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021-May-14, Tom Lane wrote:

> An idea I'd been toying with was to make invals probabilistic, that is
> there would be X% chance of an inval being forced at any particular
> opportunity. Then you could dial X up or down to make a tradeoff
> between speed and the extent of coverage you get from a single run.
> (Over time, you could expect pretty complete coverage even with X
> not very close to 1, I think.)

Maybe we could say that debug_invalidate_system_caches_always=2 means to
use the current behavior, and debug_invalidate_system_caches_always=1
uses some probabilistic rule?

--
Álvaro Herrera Valdivia, Chile

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-05-14 21:38:48 Re: Some other CLOBBER_CACHE_ALWAYS culprits
Previous Message Andres Freund 2021-05-14 21:25:53 Re: Some other CLOBBER_CACHE_ALWAYS culprits