Fix initialization of fake LSN for unlogged relations

[postgresql] / src / backend / access / transam / varsup.c

diff --git a/src/backend/access/transam/varsup.c b/src/backend/access/transam/varsup.c
index 788b961ef0ec683c46cf1536f1d6a89a81d9f9a2..b18eee42d4855899e5a13666f70f5861496b1baa 100644 (file)
--- a/src/backend/access/transam/varsup.c
+++ b/src/backend/access/transam/varsup.c
@@ -488,7 +488,7 @@ ForceTransactionIdLimitUpdate(void)
        if (!TransactionIdIsValid(xidVacLimit))
                return true;                    /* this shouldn't happen anymore either */
        if (TransactionIdFollowsOrEquals(nextXid, xidVacLimit))
-               return true;                    /* past VacLimit, don't delay updating */
+               return true;                    /* past xidVacLimit, don't delay updating */
        if (!SearchSysCacheExists1(DATABASEOID, ObjectIdGetDatum(oldestXidDB)))
                return true;                    /* could happen, per comments above */
        return false;
@@ -520,7 +520,7 @@ GetNewObjectId(void)
         * Check for wraparound of the OID counter.  We *must* not return 0
         * (InvalidOid), and in normal operation we mustn't return anything below
         * FirstNormalObjectId since that range is reserved for initdb (see
-        * IsCatalogClass()).  Note we are relying on unsigned comparison.
+        * IsCatalogRelationOid()).  Note we are relying on unsigned comparison.
         *
         * During initdb, we start the OID generator at FirstBootstrapObjectId, so
         * we only wrap if before that point when in bootstrap or standalone mode.