On 2/3/17 7:34 PM, Andres Freund wrote:
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 ;)
In my defense, there's at least one mention of 'ring buffer' in
storage/buffers. I thought there were more.
Yet more reason to just get rid of them ;P
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
