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:56:11 -0300 |
commit | 3451faaec81c8d19acdb243bfc22598c33ab074d (patch) | |
tree | 7556990ce8e40d7a07488c8681c1a37bbe46f7ab /src/backend/access/transam/multixact.c | |
parent | 374652fb6dc53a12f79586ce0e77f1ec22d58a80 (diff) | |
download | postgresql-3451faaec81c8d19acdb243bfc22598c33ab074d.tar.gz postgresql-3451faaec81c8d19acdb243bfc22598c33ab074d.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.c | 2 |
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 |