Commit cca705a
committed
Fix bug in SetOffsetVacuumLimit() triggered by find_multixact_start() failure.
Previously, if find_multixact_start() failed, SetOffsetVacuumLimit() would
install 0 into MultiXactState->offsetStopLimit if it previously succeeded.
Luckily, there are no known cases where find_multixact_start() will return
an error in 9.5 and above. But if it were to happen, for example due to
filesystem permission issues, it'd be somewhat bad: GetNewMultiXactId()
could continue allocating mxids even if close to a wraparound, or it could
erroneously stop allocating mxids, even if no wraparound is looming. The
wrong value would be corrected the next time SetOffsetVacuumLimit() is
called, or by a restart.
Reported-By: Noah Misch, although this is not his preferred fix
Discussion: 20151210140450.GA22278@alap3.anarazel.de
Backpatch: 9.5, where the bug was introduced as part of 4f627f1 parent 2a35449 commit cca705a
1 file changed
+6
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2552 | 2552 | | |
2553 | 2553 | | |
2554 | 2554 | | |
| 2555 | + | |
2555 | 2556 | | |
2556 | 2557 | | |
2557 | 2558 | | |
| |||
2566 | 2567 | | |
2567 | 2568 | | |
2568 | 2569 | | |
| 2570 | + | |
2569 | 2571 | | |
2570 | 2572 | | |
2571 | 2573 | | |
| |||
2633 | 2635 | | |
2634 | 2636 | | |
2635 | 2637 | | |
2636 | | - | |
2637 | | - | |
| 2638 | + | |
| 2639 | + | |
| 2640 | + | |
2638 | 2641 | | |
2639 | 2642 | | |
2640 | 2643 | | |
| 2644 | + | |
2641 | 2645 | | |
2642 | 2646 | | |
2643 | 2647 | | |
| |||
0 commit comments