Skip to content

be tolerant when parsing the postgres version #112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

be tolerant when parsing the postgres version #112

wants to merge 1 commit into from

Conversation

rgl
Copy link

@rgl rgl commented Oct 8, 2017

No description provided.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 53.951% when pulling f2731fa on rgl:master into 6e3d130 on wrouesnel:master.

@wrouesnel
Copy link
Contributor

We don't particularly want to be more tolerant about version mismatches, since it can lead to subtly incorrect metrics (not a situation you want to be in).

The correct fix here is to handle the 10.x version transition with the semver library properly, which will probably involve just appending a .0 so it looks right. I'll upload a patch soon.

wrouesnel added a commit that referenced this pull request Oct 9, 2017
@rgl
Copy link
Author

rgl commented Oct 9, 2017

I'm not seeing why ParseTolerant is not a good fit, since it pretty much does that.

@wrouesnel
Copy link
Contributor

You're right it is! I have an alternate fix sitting on another PR (adds a better regex check) but the integration tests are not reporting full metrics for postgres 10 yet so more work to do.

@wrouesnel wrouesnel closed this in cb4b628 Oct 23, 2017
ritbl referenced this pull request in heniek/postgres_exporter Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants