Andres Freund 4b4b680c3d Make backend local tracking of buffer pins memory efficient. ... Since the dawn of time (aka Postgres95) multiple pins of the same buffer by one backend have been optimized not to modify the shared refcount more than once. This optimization has always used a NBuffer sized array in each backend keeping track of a backend's pins. That array (PrivateRefCount) was one of the biggest per-backend memory allocations, depending on the shared_buffers setting. Besides the waste of memory it also has proven to be a performance bottleneck when assertions are enabled as we make sure that there's no remaining pins left at the end of transactions. Also, on servers with lots of memory and a correspondingly high shared_buffers setting the amount of random memory accesses can also lead to poor cpu cache efficiency. Because of these reasons a backend's buffers pins are now kept track of in a small statically sized array that overflows into a hash table when necessary. Benchmarks have shown neutral to positive performance results with considerably lower memory usage. Patch by me, review by Robert Haas. Discussion: 20140321182231.GA17111@alap3.anarazel.de		2014-08-30 14:03:21 +02:00
..
Makefile
pg_buffercache_pages.c	Make backend local tracking of buffer pins memory efficient.	2014-08-30 14:03:21 +02:00
pg_buffercache--1.0--1.1.sql
pg_buffercache--1.1.sql
pg_buffercache--unpackaged--1.0.sql
pg_buffercache.control