From aab57d260ca5268f86d7591ce7957f3b0d68a517 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Wed, 18 Dec 2024 11:47:32 +0200 Subject: [PATCH v10 05/14] Fixup setting oldestOffset --- src/backend/access/transam/multixact.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/backend/access/transam/multixact.c b/src/backend/access/transam/multixact.c index a817f539ee9..3d27995a299 100644 --- a/src/backend/access/transam/multixact.c +++ b/src/backend/access/transam/multixact.c @@ -1045,9 +1045,7 @@ GetNewMultiXactId(int nmembers, MultiXactOffset *offset) * against catastrophic data loss due to multixact wraparound. The basic * rules are: * - * If we're past multiVacLimit or the safe threshold for member storage - * space, or we don't know what the safe threshold for member storage is, - * start trying to force autovacuum cycles. + * If we're past multiVacLimit, start trying to force autovacuum cycles. * If we're past multiWarnLimit, start issuing warnings. * If we're past multiStopLimit, refuse to create new MultiXactIds. * @@ -2695,7 +2693,7 @@ SetOffsetVacuumLimit(bool is_startup) * overrun of old data in the members SLRU area. We can only do so if the * oldest offset is known though. */ - if (prevOldestOffsetKnown) + if (!oldestOffsetKnown && prevOldestOffsetKnown) { /* * If we failed to get the oldest offset this time, but we have a -- 2.39.5