From 66c5bd3a6fd8a4c317412838ab3870ab251833b6 Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Mon, 1 Jul 2019 22:28:08 -0700 Subject: [PATCH] Remove obsolete nbtree "get root" comment. 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 --- src/backend/access/nbtree/nbtpage.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/backend/access/nbtree/nbtpage.c b/src/backend/access/nbtree/nbtpage.c index 03570300d8..50455db9af 100644 --- a/src/backend/access/nbtree/nbtpage.c +++ b/src/backend/access/nbtree/nbtpage.c @@ -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 * 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 - * standard class of race conditions exists here; I think I covered - * them all in the intricate dance of lock requests below. + * itself. If no root page exists yet, we have to create one. * * The access type parameter (BT_READ or BT_WRITE) controls whether * a new root page will be created or not. If access = BT_READ, -- 2.40.0