> ISTM that vacuum_xid_failsafe_check() should really be doing something
> similar. For example, it could prorate using
> vacuum_multixact_failsafe_age, calculating a member-space-wise
> threshold to trigger the failsafe at, independent of
> mxid_age(relminmxid) itself.
+1. For the case mentioned
Some of you might have already seen the recent postmortem from
Metronome, which involves an outage caused by MultiXact Member
exhaustion:
https://metronome.com/blog/root-cause-analysis-postgresql-multixact-member-exhaustion-incidents-may-2025
This reminded me of the fact that vacuum_multixact_fai
