From: Peter Geoghegan <pg@bowt.ie>
Date: Sat, 12 Mar 2022 03:30:21 +0000 (-0800)
Subject: Normalize heap_prepare_freeze_tuple argument name.
X-Git-Tag: REL_15_BETA1~556
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5b68f75e12831cd5b7d8058320c0ca29bbe76067;p=thirdparty%2Fpostgresql.git

Normalize heap_prepare_freeze_tuple argument name.

We called the argument totally_frozen in its function prototype as well
as in code comments, even though totally_frozen_p was used in the
function definition.  Standardize on totally_frozen.
---

diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 4e6aeba3154..3746336a09d 100644
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -6417,7 +6417,7 @@ FreezeMultiXactId(MultiXactId multi, uint16 t_infomask,
  * are older than the specified cutoff XID and cutoff MultiXactId.  If so,
  * setup enough state (in the *frz output argument) to later execute and
  * WAL-log what we would need to do, and return true.  Return false if nothing
- * is to be changed.  In addition, set *totally_frozen_p to true if the tuple
+ * is to be changed.  In addition, set *totally_frozen to true if the tuple
  * will be totally frozen after these operations are performed and false if
  * more freezing will eventually be required.
  *
@@ -6445,7 +6445,7 @@ bool
 heap_prepare_freeze_tuple(HeapTupleHeader tuple,
 						  TransactionId relfrozenxid, TransactionId relminmxid,
 						  TransactionId cutoff_xid, TransactionId cutoff_multi,
-						  xl_heap_freeze_tuple *frz, bool *totally_frozen_p)
+						  xl_heap_freeze_tuple *frz, bool *totally_frozen)
 {
 	bool		changed = false;
 	bool		xmax_already_frozen = false;
@@ -6645,8 +6645,8 @@ heap_prepare_freeze_tuple(HeapTupleHeader tuple,
 		}
 	}
 
-	*totally_frozen_p = (xmin_frozen &&
-						 (freeze_xmax || xmax_already_frozen));
+	*totally_frozen = (xmin_frozen &&
+					   (freeze_xmax || xmax_already_frozen));
 	return changed;
 }