Re: Bug: Buffer cache is not scan resistant

"Simon Riggs"  writes:
> Itakgaki-san and I were discussing in January the idea of cache-looping,
> whereby a process begins to reuse its own buffers in a ring of ~32
> buffers. When we cycle back round, if usage_count==1 then we assume that
> we can reuse that buffer. This avoids cache swamping for read and write
> workloads, plus avoids too-frequent WAL writing for VACUUM.

> This would maintain the beneficial behaviour for OLTP,

Justify that claim.  It sounds to me like this would act very nearly the
same as having shared_buffers == 32 ...
		regards, tom lane