-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update Posgres to psycopg3 #19322
Merged
Merged
Update Posgres to psycopg3 #19322
Conversation
This file contains 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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
lu-zhengda
approved these changes
Jan 22, 2025
iliakur
approved these changes
Jan 22, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jan 22, 2025
* WIP * WIP * Changelog * Changelog * Dep * License * License * Lint * Fix * Build deps * E2E * Lint * +x b13f5e0
sethsamuel
added a commit
that referenced
this pull request
Jan 28, 2025
This reverts commit b13f5e0.
iliakur
pushed a commit
that referenced
this pull request
Jan 28, 2025
* Revert "Update Posgres to psycopg3 (#19322)" This reverts commit b13f5e0. * Changelog * Dep * Revert "Upgrade PGBouncer to psycopg3" (#19497) * Revert "Upgrade PGBouncer to psycopg3 (#19325)" This reverts commit 5b65299. * Changelog --------- Co-authored-by: Enrico Donnici <[email protected]> --------- Co-authored-by: Enrico Donnici <[email protected]>
datadog-agent-integrations-bot bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
* Revert "Update Posgres to psycopg3 (#19322)" This reverts commit b13f5e0. * Changelog * Dep * Revert "Upgrade PGBouncer to psycopg3" (#19497) * Revert "Upgrade PGBouncer to psycopg3 (#19325)" This reverts commit 5b65299. * Changelog --------- Co-authored-by: Enrico Donnici <[email protected]> --------- Co-authored-by: Enrico Donnici <[email protected]> (cherry picked from commit a74f10a)
github-actions bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
* Revert "Update Posgres to psycopg3 (#19322)" This reverts commit b13f5e0. * Changelog * Dep * Revert "Upgrade PGBouncer to psycopg3" (#19497) * Revert "Upgrade PGBouncer to psycopg3 (#19325)" This reverts commit 5b65299. * Changelog --------- Co-authored-by: Enrico Donnici <[email protected]> --------- Co-authored-by: Enrico Donnici <[email protected]> a74f10a
nubtron
added a commit
that referenced
this pull request
Jan 28, 2025
Co-authored-by: Enrico Donnici <[email protected]> Co-authored-by: Seth Samuel <[email protected]>
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?
Upgrades psycopg to version 3 for Postgres integration.
DBMON-4859
Motivation
psycopg2 is deprecated and has not been updated in quite some time.
Review checklist (to be filled by reviewers)
The previous attempt at this upgrade caused problems in the Datadog cluster agents. This will need to be tested in staging extensively during RC.
qa/skip-qa
label 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