diff options
Diffstat (limited to 'src/backend/commands/vacuum.c')
-rw-r--r-- | src/backend/commands/vacuum.c | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/src/backend/commands/vacuum.c b/src/backend/commands/vacuum.c index c984488e034..641c740268a 100644 --- a/src/backend/commands/vacuum.c +++ b/src/backend/commands/vacuum.c @@ -327,10 +327,10 @@ get_rel_oids(Oid relid, const RangeVar *vacrel) * Since we don't take a lock here, the relation might be gone, or the * RangeVar might no longer refer to the OID we look up here. In the * former case, VACUUM will do nothing; in the latter case, it will - * process the OID we looked up here, rather than the new one. - * Neither is ideal, but there's little practical alternative, since - * we're going to commit this transaction and begin a new one between - * now and then. + * process the OID we looked up here, rather than the new one. Neither + * is ideal, but there's little practical alternative, since we're + * going to commit this transaction and begin a new one between now + * and then. */ relid = RangeVarGetRelid(vacrel, NoLock, false); @@ -471,7 +471,7 @@ vacuum_set_xid_limits(int freeze_min_age, if (multiXactFrzLimit != NULL) { - MultiXactId mxLimit; + MultiXactId mxLimit; /* * simplistic multixactid freezing: use the same freezing policy as @@ -711,7 +711,7 @@ vac_update_datfrozenxid(void) SysScanDesc scan; HeapTuple classTup; TransactionId newFrozenXid; - MultiXactId newFrozenMulti; + MultiXactId newFrozenMulti; bool dirty = false; /* @@ -723,8 +723,8 @@ vac_update_datfrozenxid(void) newFrozenXid = GetOldestXmin(true, true); /* - * Similarly, initialize the MultiXact "min" with the value that would - * be used on pg_class for new tables. See AddNewRelationTuple(). + * Similarly, initialize the MultiXact "min" with the value that would be + * used on pg_class for new tables. See AddNewRelationTuple(). */ newFrozenMulti = GetOldestMultiXactId(); @@ -900,8 +900,8 @@ vac_truncate_clog(TransactionId frozenXID, MultiXactId frozenMulti) /* * Update the wrap limit for GetNewTransactionId and creation of new - * MultiXactIds. Note: these functions will also signal the postmaster for - * an(other) autovac cycle if needed. XXX should we avoid possibly + * MultiXactIds. Note: these functions will also signal the postmaster + * for an(other) autovac cycle if needed. XXX should we avoid possibly * signalling twice? */ SetTransactionIdLimit(frozenXID, oldestxid_datoid); |