Re: Protect syscache from bloating with negative cache entries

At Mon, 21 Jan 2019 17:22:55 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20190121(dot)172255(dot)226467552(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
> An option is an additional PGPROC member and interface functions.
>
> struct PGPROC
> {
> ...
> int syscahe_usage_track_interval; /* track interval, 0 to disable */
>
> =# select syscahce_usage_track_add(<pid>, <intvl>[, <repetition>]);
> =# select syscahce_usage_track_remove(2134);
>
>
> Or, just provide an one-shot triggering function.
>
> =# select syscahce_take_usage_track(<pid>);
>
> This can use both a similar PGPROC variable or SendProcSignal()
> but the former doesn't fire while idle time unless using timer.

The attached is revised version of this patchset, where the third
patch is the remote setting feature. It uses static shared memory.

=# select pg_backend_catcache_stats(<pid>, <millis>);

Activates or changes catcache stats feature on the backend with
PID. (The name should be changed to .._syscache_stats, though.)
It is far smaller than the remote-GUC feature. (It contains a
part that should be in the previous patch. I will fix it later.)

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center