pgsql: Remove obsolete nbtree insertion comment. - Mailing list pgsql-committers

From Peter Geoghegan
Subject pgsql: Remove obsolete nbtree insertion comment.
Date
Msg-id E1hR3jV-0005Wz-Vk@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Remove obsolete nbtree insertion comment.

Remove a Berkeley-era comment above _bt_insertonpg() that admonishes the
reader to grok Lehman and Yao's paper before making any changes.  This
made a certain amount of sense back when _bt_insertonpg() was
responsible for most of the things that are now spread across
_bt_insertonpg(), _bt_findinsertloc(), _bt_insert_parent(), and
_bt_split(), but it doesn't work like that anymore.

I believe that this comment alludes to the need to "couple" or "crab"
buffer locks as we ascend the tree as page splits cascade upwards.  The
nbtree README already explains this in detail, which seems sufficient.
Besides, the changes to page splits made by commit 40dae7ec537 altered
the exact details of how buffer locks are retained during splits; Lehman
and Yao's original algorithm seems to release the lock on the left child
page/buffer slightly earlier than _bt_insertonpg()/_bt_insert_parent()
can.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/489e431ba56b10f5736fb54a045ca40880f11bbc

Modified Files
--------------
src/backend/access/nbtree/nbtinsert.c | 3 ---
1 file changed, 3 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Remove no-longer-used typedef.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix partition pruning to treat stable comparison operatorsprope