mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
Rename various "freeze multixact" variables
It seems to make more sense to use "cutoff multixact" terminology throughout the backend code; "freeze" is associated with replacing of an Xid with FrozenTransactionId, which is not what we do for MultiXactIds. Andres Freund Some adjustments by Álvaro Herrera
This commit is contained in:
@ -129,8 +129,8 @@ typedef struct RewriteStateData
|
||||
* determine tuple visibility */
|
||||
TransactionId rs_freeze_xid;/* Xid that will be used as freeze cutoff
|
||||
* point */
|
||||
MultiXactId rs_freeze_multi;/* MultiXactId that will be used as freeze
|
||||
* cutoff point for multixacts */
|
||||
MultiXactId rs_cutoff_multi;/* MultiXactId that will be used as cutoff
|
||||
* point for multixacts */
|
||||
MemoryContext rs_cxt; /* for hash tables and entries and tuples in
|
||||
* them */
|
||||
HTAB *rs_unresolved_tups; /* unmatched A tuples */
|
||||
@ -180,7 +180,7 @@ static void raw_heap_insert(RewriteState state, HeapTuple tup);
|
||||
* new_heap new, locked heap relation to insert tuples to
|
||||
* oldest_xmin xid used by the caller to determine which tuples are dead
|
||||
* freeze_xid xid before which tuples will be frozen
|
||||
* freeze_multi multixact before which multis will be frozen
|
||||
* min_multi multixact before which multis will be removed
|
||||
* use_wal should the inserts to the new heap be WAL-logged?
|
||||
*
|
||||
* Returns an opaque RewriteState, allocated in current memory context,
|
||||
@ -188,7 +188,7 @@ static void raw_heap_insert(RewriteState state, HeapTuple tup);
|
||||
*/
|
||||
RewriteState
|
||||
begin_heap_rewrite(Relation new_heap, TransactionId oldest_xmin,
|
||||
TransactionId freeze_xid, MultiXactId freeze_multi,
|
||||
TransactionId freeze_xid, MultiXactId cutoff_multi,
|
||||
bool use_wal)
|
||||
{
|
||||
RewriteState state;
|
||||
@ -218,7 +218,7 @@ begin_heap_rewrite(Relation new_heap, TransactionId oldest_xmin,
|
||||
state->rs_use_wal = use_wal;
|
||||
state->rs_oldest_xmin = oldest_xmin;
|
||||
state->rs_freeze_xid = freeze_xid;
|
||||
state->rs_freeze_multi = freeze_multi;
|
||||
state->rs_cutoff_multi = cutoff_multi;
|
||||
state->rs_cxt = rw_cxt;
|
||||
|
||||
/* Initialize hash tables used to track update chains */
|
||||
@ -347,7 +347,7 @@ rewrite_heap_tuple(RewriteState state,
|
||||
* very-old xmin or xmax, so that future VACUUM effort can be saved.
|
||||
*/
|
||||
heap_freeze_tuple(new_tuple->t_data, state->rs_freeze_xid,
|
||||
state->rs_freeze_multi);
|
||||
state->rs_cutoff_multi);
|
||||
|
||||
/*
|
||||
* Invalid ctid means that ctid should point to the tuple itself. We'll
|
||||
|
Reference in New Issue
Block a user