Clarify comment on multixid offset wraparound check
Coverity complained that offset cannot be 0 here because there's an
explicit check for "offset == 0" earlier in the function, but it
didn't see the possibility that offset could've wrapped around to 0.
The code is correct, but clarify the comment about it.
The same code exists in backbranches in the server
GetMultiXactIdMembers() function and in 'master' in the pg_upgrade
GetOldMultiXactIdSingleMember function. In backbranches Coverity
didn't complain about it because the check was merely an assertion,
but change the comment in all supported branches for consistency.
Per Tom Lane's suggestion.
Discussion: https://www.postgresql.org/message-id/1827755.1765752936@sss.pgh.pa.us
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/cd1a887fe9bfdfcc7a2e2ba5145123c892197648
Modified Files
--------------
src/backend/access/transam/multixact.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
