Re: [HACKERS] Clock with Adaptive Replacement

On Wed, May 2, 2018 at 3:06 PM, Vladimir Sitnikov
<sitnikov.vladimir@gmail.com> wrote:
> Sample output can be seen here:
> https://github.com/vlsi/pgsqlstat/tree/pgsqlio#pgsqlio

Neat.  Not sure what generated this trace, but note this part:

3271838881374    88205        0        0     1663    16385    16604      0
 3271840973321     4368        0        0     1663    16385    16604      1
 3271842680626     4502        0        0     1663    16385    16604      1
 3271846077927     4173        0        0     1663    16385    16604      1

If we want to avoid artificial inflation of usage counts, that kind of
thing would be a good place to start -- obviously 4 consecutive
accesses to the same buffer by the same backend doesn't justify a
separate usage count bump each time.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company