Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ce2a860

Browse files
Update obsolete nbtree deletion comments.
_bt_delitems_delete() is no longer the high-level entry point used by index tuple deletion driven by index tuples whose LP_DEAD bits are set (now called "simple index tuple deletion"). It became a lower level routine that's only called by _bt_delitems_delete_check() following commit d168b66.
1 parent c1a47df commit ce2a860

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/access/nbtree/nbtpage.c

+2-2
Original file line numberDiff line numberDiff line change
@@ -1197,7 +1197,7 @@ _bt_delitems_vacuum(Relation rel, Buffer buf,
11971197
*
11981198
* PageIndexTupleOverwrite() won't unset each item's LP_DEAD bit when it
11991199
* happens to already be set. It's important that we not interfere with
1200-
* _bt_delitems_delete().
1200+
* any future simple index tuple deletion operations.
12011201
*/
12021202
for (int i = 0; i < nupdatable; i++)
12031203
{
@@ -1230,7 +1230,7 @@ _bt_delitems_vacuum(Relation rel, Buffer buf,
12301230
* This flag indicates the presence of LP_DEAD items on the page (though
12311231
* not reliably). Note that we only rely on it with pg_upgrade'd
12321232
* !heapkeyspace indexes. That's why clearing it here won't usually
1233-
* interfere with _bt_delitems_delete().
1233+
* interfere with simple index tuple deletion.
12341234
*/
12351235
opaque->btpo_flags &= ~BTP_HAS_GARBAGE;
12361236

0 commit comments

Comments
 (0)