fix(compute): use proper safekeeper in VotesCollectedMset (#12175)

## Problem
`VotesCollectedMset` uses the wrong safekeeper to update truncateLsn.
This led to some failed assert later in the code during running
safekeeper migration tests.
- Relates to https://github.com/neondatabase/neon/issues/11823

## Summary of changes
Use proper safekeeper to update truncateLsn in VotesCollectedMset
This commit is contained in:
Dmitrii Kovalkov
2025-06-10 11:16:42 +04:00
committed by GitHub
parent 40d7583906
commit 73be6bb736

View File

@@ -1135,7 +1135,7 @@ VotesCollectedMset(WalProposer *wp, MemberSet *mset, Safekeeper **msk, StringInf
wp->propTermStartLsn = sk->voteResponse.flushLsn; wp->propTermStartLsn = sk->voteResponse.flushLsn;
wp->donor = sk; wp->donor = sk;
} }
wp->truncateLsn = Max(wp->safekeeper[i].voteResponse.truncateLsn, wp->truncateLsn); wp->truncateLsn = Max(sk->voteResponse.truncateLsn, wp->truncateLsn);
if (n_votes > 0) if (n_votes > 0)
appendStringInfoString(s, ", "); appendStringInfoString(s, ", ");