-
- Downloads
Arrange to cache btree metapage data in the relcache entry for the index,
thereby saving a visit to the metapage in most index searches/updates. This wouldn't actually save any I/O (since in the old regime the metapage generally stayed in cache anyway), but it does provide a useful decrease in bufmgr traffic in high-contention scenarios. Per my recent proposal.
Showing
- src/backend/access/nbtree/README 12 additions, 2 deletionssrc/backend/access/nbtree/README
- src/backend/access/nbtree/nbtinsert.c 9 additions, 2 deletionssrc/backend/access/nbtree/nbtinsert.c
- src/backend/access/nbtree/nbtpage.c 72 additions, 2 deletionssrc/backend/access/nbtree/nbtpage.c
- src/backend/access/nbtree/nbtree.c 13 additions, 1 deletionsrc/backend/access/nbtree/nbtree.c
- src/backend/utils/cache/relcache.c 7 additions, 1 deletionsrc/backend/utils/cache/relcache.c
- src/include/utils/rel.h 9 additions, 1 deletionsrc/include/utils/rel.h
Loading
Please register or sign in to comment