Bump libpq version for Postgres 18 #22068
Open
+7
−7
Conversation
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
datadog-agent-integrations-bot
bot
added
team/agent-integrations
team/agent-build
labels
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
Contributor
Author
|
aarch64 build failure looks to be due to libpq 18.0 breaking on manylinux2014. Upstream bug report 😞 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
With the release of Postgres 18 and the recent support added to the Postgres integration for Postgres 18 we should update the libpq version we build the psycopg wheels against in order for customers monitoring Postgres 18 versions (and Postgres 17 as we seem to have let that slip 😅) benefit from all new client side support that might be available. libpq maintains strong backwards compatibility with older clients and gracefully drops wire protocol support when using an older client version against a new Postgres server so this bump shouldn't have negative impact on existing usage
Motivation
I recently added support for Postgres 18 and noticed we're still on quite an old libpq version. We purposely skipped this a few months ago when upgrading from psycopg2 -> psycopg3, but now that we're past that hurdle we should get this on a newer version.
Newer libpq versions also contain a number of CVE fixes
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged