Re: Some other CLOBBER_CACHE_ALWAYS culprits
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Some other CLOBBER_CACHE_ALWAYS culprits |
| Дата | |
| Msg-id | 20210514213651.GA27122@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Some other CLOBBER_CACHE_ALWAYS culprits (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Some other CLOBBER_CACHE_ALWAYS culprits
|
| Список | 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
В списке pgsql-hackers по дате отправления: