Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit c330842

Browse files
committed
Reorganize heap_page_prune() function comment
heap_page_prune()'s function header comment didn't explain the parameters in the same order they appear in the function. Fix that. Author: Melanie Plageman <melanieplageman@gmail.com> Discussion: https://www.postgresql.org/message-id/20240320013602.6sypr4cx6sefpemg@liskov
1 parent 522ed12 commit c330842

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

src/backend/access/heap/pruneheap.c

+6-7
Original file line numberDiff line numberDiff line change
@@ -197,18 +197,17 @@ heap_page_prune_opt(Relation relation, Buffer buffer)
197197
* array following array truncation by us.
198198
*
199199
* vistest is used to distinguish whether tuples are DEAD or RECENTLY_DEAD
200-
* (see heap_prune_satisfies_vacuum and
201-
* HeapTupleSatisfiesVacuum).
200+
* (see heap_prune_satisfies_vacuum).
202201
*
203-
* mark_unused_now indicates whether or not dead items can be set LP_UNUSED during
204-
* pruning.
205-
*
206-
* off_loc is the offset location required by the caller to use in error
207-
* callback.
202+
* mark_unused_now indicates whether or not dead items can be set LP_UNUSED
203+
* during pruning.
208204
*
209205
* presult contains output parameters needed by callers such as the number of
210206
* tuples removed and the number of line pointers newly marked LP_DEAD.
211207
* heap_page_prune() is responsible for initializing it.
208+
*
209+
* off_loc is the offset location required by the caller to use in error
210+
* callback.
212211
*/
213212
void
214213
heap_page_prune(Relation relation, Buffer buffer,

0 commit comments

Comments
 (0)