On 09/12/2025 14:00, Heikki Linnakangas wrote:
> 1. Currently, at multixid wraparound, MultiXactState->nextMXact goes to
> 0, which is invalid. All the readers must be prepared for that, and skip
> over the 0. That's error-prone, we've already missed that a few times.
> Let's change things so that the code that *writes* MultiXactState-
> >nextMXact skips over the zero already.
Here's a patch for that. Does anyone see a problem with this?
- Heikki