Skip to content

Commit 0f6aa89

Browse files
Remove obsolete nbtree relation extension comment.
Commit 0d1fe9f improved the approach that vacuumlazy.c takes when it encounters an empty heap page. It no acquires the relation extension lock.
1 parent 6320806 commit 0f6aa89

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

src/backend/access/nbtree/nbtree.c

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -963,11 +963,10 @@ btvacuumscan(IndexVacuumInfo *info, IndexBulkDeleteResult *stats,
963963
* recycled. Taking the lock synchronizes things enough to prevent a
964964
* problem: either num_pages won't include the new page, or _bt_getbuf
965965
* already has write lock on the buffer and it will be fully initialized
966-
* before we can examine it. (See also vacuumlazy.c, which has the same
967-
* issue.) Also, we need not worry if a page is added immediately after
968-
* we look; the page splitting code already has write-lock on the left
969-
* page before it adds a right page, so we must already have processed any
970-
* tuples due to be moved into such a page.
966+
* before we can examine it. Also, we need not worry if a page is added
967+
* immediately after we look; the page splitting code already has
968+
* write-lock on the left page before it adds a right page, so we must
969+
* already have processed any tuples due to be moved into such a page.
971970
*
972971
* We can skip locking for new or temp relations, however, since no one
973972
* else could be accessing them.

0 commit comments

Comments
 (0)