Fix MultiXact wraparound calculation by using mxid_age() instead of a…#266
Merged
cherts merged 2 commits intocherts:release/0.15from Jan 13, 2026
Merged
Fix MultiXact wraparound calculation by using mxid_age() instead of a…#266cherts merged 2 commits intocherts:release/0.15from
cherts merged 2 commits intocherts:release/0.15from
Conversation
…ge() Description This PR fixes an incorrect calculation in the postgres_xacts_left_before_wraparound metric related to MultiXact IDs. Currently, the query uses the age() function for values derived from datminmxid. However, according to the PostgreSQL documentation, age() is intended for transaction IDs (XID) and must not be used for MultiXact IDs (MXID). PostgreSQL provides a dedicated function for this purpose: "mxid_age (xid) → integer Returns the number of multixact IDs between the supplied multixact ID and the current multixacts counter." — PostgreSQL Documentation - https://www.postgresql.org/docs/14/functions-info.html Using age(datminmxid) results in incorrect values because it implicitly treats a MultiXact ID as a transaction ID, which leads to inflated ages and false wraparound alerts. This PR replaces age() with mxid_age() for the MultiXact-related part of the metric, which aligns the calculation with PostgreSQL documentation and eliminates false positives.
Owner
|
Hi, @korlenko your fix and comment is correct, thanks, but the query still seems to have an small error In the expression I think this expression should be |
Author
|
Hi, @cherts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ge()
Description
This PR fixes an incorrect calculation in the postgres_xacts_left_before_wraparound metric related to MultiXact IDs. Currently, the query uses the age() function for values derived from datminmxid. However, according to the PostgreSQL documentation, age() is intended for transaction IDs (XID) and must not be used for MultiXact IDs (MXID).
PostgreSQL provides a dedicated function for this purpose: "mxid_age (xid) → integer
Returns the number of multixact IDs between the supplied multixact ID and the current multixacts counter." — PostgreSQL Documentation - https://www.postgresql.org/docs/14/functions-info.html
Using age(datminmxid) results in incorrect values because it implicitly treats a MultiXact ID as a transaction ID, which leads to inflated ages and false wraparound alerts.
This PR replaces age() with mxid_age() for the MultiXact-related part of the metric, which aligns the calculation with PostgreSQL documentation and eliminates false positives.