RE: SLRU statistics

tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>

From: "tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>

To: 'Tomas Vondra' <tomas.vondra@2ndquadrant.com>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2020-01-20T01:04:33Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix async.c to not register any SLRU stats counts in the postmaster.
- 7fd89f4d7a51 13.0 landed
Use proper GetDatum function in pg_stat_get_slru().
- 043e3e040160 13.0 landed
Initialize SLRU stats entries to zero.
- f3d23d83ef9a 13.0 landed
Remove pg_xact from pg_stat_reset_slru docs
- e685ca63ca4f 13.0 landed
Remove pg_xact entry from SLRU stats
- 2e08d314ed07 13.0 landed
Track SLRU page hits in SimpleLruReadPage_ReadOnly
- 2b88fdde30d8 13.0 landed
Fix typo in SLRU stats documentation
- 2c220ca46f3f 13.0 landed
Collect statistics about SLRU caches
- 28cac71bd368 13.0 landed
Simplify and rename some GUC variables, per various recent discussions:
- 48f7e6439568 8.3.0 cited

From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
> One of the stats I occasionally wanted to know are stats for the SLRU
> stats (we have couple of those - clog, subtrans, ...). So here is a WIP
> version of a patch adding that.

How can users take advantage of this information?  I think we also need the ability to set the size of SLRU buffers.  (I want to be freed from the concern about the buffer shortage by setting the buffer size to its maximum.  For example, CLOG would be only 1 GB.)


Regards
Takayuki Tsunakawa