-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
PostgreSQL: Fix tls certificate issue by downgrading lib/pq #67372
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
given the diff between the two versions
I think it's safe to downgrade it
@@ -73,7 +73,7 @@ require ( | |||
github.com/jmespath/go-jmespath v0.4.0 | |||
github.com/json-iterator/go v1.1.12 | |||
github.com/jung-kurt/gofpdf v1.16.2 | |||
github.com/lib/pq v1.10.7 | |||
github.com/lib/pq v1.10.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest adding a comment to prevent future attempts to upgrade until this is fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @papagian added a comment at the bottom. Is that okay?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 I don't see any harm in downgrading based on looking at lib/pq@v1.10.6...v1.10.9 and lib/pq@v1.10.6...v1.10.7
* PostgreSQL: Downgrade lib/pq * Add comment (cherry picked from commit 5c32925)
This PR tries to fix the issue stated in #65816 by downgrading the lib/pq library.
Which issue(s) does this PR fix?:
Fixes #65816