database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-05 07:41:25 +03:00
Code Activity

Remove obsolete nbtree relation extension comment.

Browse Source 
Commit 0d1fe9f7 improved the approach that vacuumlazy.c takes when it
encounters an empty heap page.  It no acquires the relation extension
lock.
This commit is contained in:
Peter Geoghegan
2021-08-31 16:55:39 -07:00
parent 6320806ac3
commit 0f6aa893cb
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/backend/access/nbtree/nbtree.c
View File

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