The new MultiXact freezing routines introduced by commit
8e9a16ab8f7
neglected to consider tuples that came from a pg_upgrade'd database; a
vacuum run that tried to freeze such tuples would die with an error such
as
ERROR: MultiXactId
11415437 does no longer exist -- apparent wraparound
To fix, ensure that GetMultiXactIdMembers is allowed to return empty
multis when the infomask bits are right, as is done in other callsites.
Per trouble report from F-Secure.
In passing, fix a copy&paste bug reported by Andrey Karpov from VIVA64
from their PVS-Studio static checked, that instead of setting relminmxid
to Invalid, we were setting relfrozenxid twice. Not an important
mistake because that code branch is about relations for which we don't
use the frozenxid/minmxid values at all in the first place, but seems to
warrants a fix nonetheless.
bool has_lockers;
TransactionId update_xid;
bool update_committed;
+ bool allow_old;
*flags = 0;
* anything.
*/
- nmembers = GetMultiXactIdMembers(multi, &members, false);
+ allow_old = !(t_infomask & HEAP_LOCK_MASK) &&
+ HEAP_XMAX_IS_LOCKED_ONLY(t_infomask);
+ nmembers = GetMultiXactIdMembers(multi, &members, allow_old);
if (nmembers <= 0)
{
/* Nothing worth keeping */
MultiXactMember *members;
int nmembers;
int i;
+ bool allow_old;
/* need to check whether any member of the mxact is too old */
- nmembers = GetMultiXactIdMembers(multi, &members, false);
+ allow_old = !(tuple->t_infomask & HEAP_LOCK_MASK) &&
+ HEAP_XMAX_IS_LOCKED_ONLY(tuple->t_infomask);
+ nmembers = GetMultiXactIdMembers(multi, &members, allow_old);
for (i = 0; i < nmembers; i++)
{
* commands/sequence.c.)
*/
new_rel_reltup->relfrozenxid = InvalidTransactionId;
- new_rel_reltup->relfrozenxid = InvalidMultiXactId;
+ new_rel_reltup->relminmxid = InvalidMultiXactId;
}
new_rel_reltup->relowner = relowner;