diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-09-16 15:45:00 -0300 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-09-16 15:47:31 -0300 |
commit | dd778e9d888454fdd2c25c66fc268ba9844eb125 (patch) | |
tree | af4993780ba80c168f5203f303015fa60a37771f /src/backend/access/heap/heapam.c | |
parent | 0892ecbc015930dde2cee9ad464b9b70fdb7667e (diff) | |
download | postgresql-dd778e9d888454fdd2c25c66fc268ba9844eb125.tar.gz postgresql-dd778e9d888454fdd2c25c66fc268ba9844eb125.zip |
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
Diffstat (limited to 'src/backend/access/heap/heapam.c')
-rw-r--r-- | src/backend/access/heap/heapam.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index b1a5d9f65ac..ead3d690aea 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -5135,8 +5135,8 @@ heap_freeze_tuple(HeapTupleHeader tuple, TransactionId cutoff_xid, /* * Note that this code handles IS_MULTI Xmax values, too, but only to mark - * the tuple frozen if the updating Xid in the mxact is below the freeze - * cutoff; it doesn't remove dead members of a very old multixact. + * the tuple as not updated if the multixact is below the cutoff Multixact + * given; it doesn't remove dead members of a very old multixact. */ xid = HeapTupleHeaderGetRawXmax(tuple); if ((tuple->t_infomask & HEAP_XMAX_IS_MULTI) ? |