You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This addresses #321 with the
fix @jackc proposed there--
The only reason we send ssl_renegotiation_limit is to avoid mysterious connection errors when connecting to servers that use renegotiation. But PostgreSQL defaults to 0 for all supported versions, and removed the setting for 9.6. So I guess all we need to do is remove the default startup parameter message. Anyone who really needs it can easily add it back with ConnConfig.RuntimeParams.
Redshift users that need to connect
w/ SSL currently fork the library to delete this parameter, e.g.
As expressed in doc.go, I think this fix should go in v3.3.0. While I doubt this breaks connections for many, I suppose it could if a user of this library ignores warnings and has a non-zero value for this parameter set in postgresql.conf in Postgres < 9.6. That said, I don't feel strongly :P
This addresses jackc#321 with the
fix @jackc proposed there. Redshift users that need to connect
w/ SSL currently fork the library to delete this parameter, e.g.
segmentio@8e0028d
And, that's annoying to keep up-to-date :)
@jackc Thanks for merging this. Would you please publish a v3.3.0 tag? Or, are you waiting on something else to do that? The docs change merged in this PR mentions this being available as of v3.30, and I'd like to pin vendor of my project that requires this fix to a release of pgx.
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.
This addresses #321 with the
fix @jackc proposed there--
Redshift users that need to connect
w/ SSL currently fork the library to delete this parameter, e.g.
segmentio@8e0028d
And, that's annoying to keep up-to-date :)