aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/multixact.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2013-09-16 15:45:00 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2013-09-16 15:47:31 -0300
commitdd778e9d888454fdd2c25c66fc268ba9844eb125 (patch)
treeaf4993780ba80c168f5203f303015fa60a37771f /src/backend/access/transam/multixact.c
parent0892ecbc015930dde2cee9ad464b9b70fdb7667e (diff)
downloadpostgresql-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/transam/multixact.c')
-rw-r--r--src/backend/access/transam/multixact.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/transam/multixact.c b/src/backend/access/transam/multixact.c
index 745b1f1d891..e3f5cbc0cd9 100644
--- a/src/backend/access/transam/multixact.c
+++ b/src/backend/access/transam/multixact.c
@@ -1069,7 +1069,7 @@ GetMultiXactIdMembers(MultiXactId multi, MultiXactMember **members,
* We check known limits on MultiXact before resorting to the SLRU area.
*
* An ID older than MultiXactState->oldestMultiXactId cannot possibly be
- * useful; it should have already been frozen by vacuum. We've truncated
+ * useful; it should have already been removed by vacuum. We've truncated
* the on-disk structures anyway. Returning the wrong values could lead
* to an incorrect visibility result. However, to support pg_upgrade we
* need to allow an empty set to be returned regardless, if the caller is