> >> I also see that we're not forcing the computation of the (M)XID > >> scores. Is that intentional? > > > > hmm, the force_score does not need to be in the force_vacuum path > > because the score is calculated there naturally when the table is in > > need of force_vacuum. The force_score is there to ensure that > > we are not existing early in the autovacuum disabled case. > > So, unless the table is beyond a freeze-max-age parameter, the (M)XID > scores will always be 0.0?
You're right after thinking about this again. There is no reason why we should treat the force_vacuum case differently. The score should still be included so someone monitoring can see the xid|mxid_age climbing well before it becomes an issue. -- Sami
