On 2017-02-03 19:26:55 -0600, Jim Nasby wrote:
> On 2/3/17 6:20 PM, Andres Freund wrote:
> > > - The ringbuffers in shared buffers can be problematic. One possible way of
> > > solving that is to get rid of ringbuffers entirely and rely on different
> > > initial values for usage_count instead, but that's not desirable if it just
> > > means more clock sweep work for backends.
> > I'm not quite sure which ringbuffer you're referring to here? If to the
> > new one, why is it problematic?
>
> No, I mean the non-default BufferAccessStrategy's.
That's not a ringbuffer that's a buffer ring ;)
