diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2023-04-03 11:31:43 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2023-04-03 11:31:43 -0700 |
| commit | e48c817395e1cdc85dbecc4ff3c18e34983ae3f2 (patch) | |
| tree | ab8c984902a3f3a41d7b4ee25067dca0254ec456 /src/backend/parser/parser.c | |
| parent | a349b86603e11bad811bec111ec5330b9908e525 (diff) | |
| download | postgresql-e48c817395e1cdc85dbecc4ff3c18e34983ae3f2.tar.gz postgresql-e48c817395e1cdc85dbecc4ff3c18e34983ae3f2.zip | |
Recycle deleted nbtree pages more aggressively.
Commit 61b313e4 made nbtree consistently pass down a heaprel to low
level routines like _bt_getbuf(). Although this was primarily intended
as preparation for logical decoding on standbys, it also made it easy to
correct an old deficiency in how nbtree VACUUM determines whether or not
it's now safe to recycle deleted pages.
Pass the heaprel to GlobalVisTestFor() in nbtree routines that deal with
recycle safety. nbtree now makes less pessimistic assumptions about
recycle safety within non-catalog relations. This enhancement
complements the recycling enhancement added by commit 9dd963ae25.
nbtree remains just as pessimistic as ever when it comes to recycle
safety within indexes on catalog relations. There is no fundamental
reason why we need to treat catalog relations differently, though. The
behavioral inconsistency is a consequence of the way that nbtree uses
nextXID values to implement what Lanin and Shasha call "the drain
technique". Note in particular that it has nothing to do with whether
or not index tuples might still be required for an older MVCC snapshot.
Author: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Discussion: https://postgr.es/m/CAH2-WzkaiDxCje0yPuH=3Uh2p1V_2pFGY==xfbZoZu7Ax_NB8g@mail.gmail.com
Diffstat (limited to 'src/backend/parser/parser.c')
0 files changed, 0 insertions, 0 deletions