Respect Hot Standby controls while recycling btree index pages.
Btree pages were recycled after VACUUM deletes all records on a
page and then a subsequent VACUUM occurs after the RecentXmin
horizon is reached. Using RecentXmin meant that we did not respond
correctly to the user controls provide to avoid Hot Standby
conflicts and so spurious conflicts could be generated in some
workload combinations. We now reuse pages only when we reach
RecentGlobalXmin, which can be much later in the presence of long
running queries and is also controlled by vacuum_defer_cleanup_age
and hot_standby_feedback.
Noah Misch and Simon Riggs
Branch
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/9340e643e4cbc11a7a5aaea0297236e9a8c07600
Modified Files
--------------
src/backend/access/nbtree/nbtpage.c | 12 ++++++++++--
1 files changed, 10 insertions(+), 2 deletions(-)