Skip to content

Commit 9debd12

Browse files
Remove comment about historic heap vacuuming issue.
Remove comment block about how heap page vacuuming used to set tuples with storage to LP_UNUSED in a rare edge case that can no longer happen following commit 8523492. The comments seem unnecessary now, since it's now generally clear that heap vacuuming only applies to LP_DEAD items from VACUUM's first heap pass following more recent work from commits 12b5ade and 4f8d9d1.
1 parent 9de692c commit 9debd12

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

src/backend/access/heap/vacuumlazy.c

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2478,13 +2478,6 @@ lazy_vacuum_heap_rel(LVRelState *vacrel)
24782478
* index is an offset into the vacrel->dead_items array for the first listed
24792479
* LP_DEAD item on the page. The return value is the first index immediately
24802480
* after all LP_DEAD items for the same page in the array.
2481-
*
2482-
* Prior to PostgreSQL 14 there were rare cases where this routine had to set
2483-
* tuples with storage to unused. These days it is strictly responsible for
2484-
* marking LP_DEAD stub line pointers as unused. This only happens for those
2485-
* LP_DEAD items on the page that were determined to be LP_DEAD items back
2486-
* when the same page was visited by lazy_scan_prune() (i.e. those whose TID
2487-
* was recorded in the dead_items array at the time).
24882481
*/
24892482
static int
24902483
lazy_vacuum_heap_page(LVRelState *vacrel, BlockNumber blkno, Buffer buffer,

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy