database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Remove obsolete nbtree "get root" comment.

Browse Source 
Remove a very old Berkeley era comment that doesn't seem to have
anything to do with the current locking considerations within
_bt_getroot().

Discussion: https://postgr.es/m/CAH2-WzmA2H+rL-xxF5o6QhMD+9x6cJTnz2Mr3Li_pbPBmqoTBQ@mail.gmail.com
This commit is contained in:
Peter Geoghegan
2019-07-01 22:28:08 -07:00
parent 2b1394fc2b
commit 66c5bd3a6f
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/access/nbtree/nbtpage.c
View File

@ -266,9 +266,7 @@ _bt_update_meta_cleanup_info(Relation rel, TransactionId oldestBtpoXact,
* *
* Since the root page can move around the btree file, we have to read * Since the root page can move around the btree file, we have to read
* its location from the metadata page, and then read the root page * its location from the metadata page, and then read the root page
* itself. If no root page exists yet, we have to create one. The * itself. If no root page exists yet, we have to create one.
* standard class of race conditions exists here; I think I covered
* them all in the intricate dance of lock requests below.
* *
* The access type parameter (BT_READ or BT_WRITE) controls whether * The access type parameter (BT_READ or BT_WRITE) controls whether
* a new root page will be created or not. If access = BT_READ, * a new root page will be created or not. If access = BT_READ,