Repository navigation
Bump version to 2.7.0 - #49
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
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
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.
Why
Ships #47 and #48 to users. Pools and reconnects no longer hang on a server that accepts a connection and then stalls, and invalid TLS or GSS modes fail before anything is sent.
Bumps the version to 2.7.0. It is a minor release because both changes tighten behavior: a value that used to pass is now rejected, and a timeout now throws a different error type. Included since 2.6.0:
Changed
sslmodeorgssencmodeis rejected with anArgumentErrorwhen a connection string is parsed or a connection is constructed, before anything is sent.validate_dsnreports it as:invalid_value. Before, the value was checked only when connecting, and with GSS encryption negotiated an invalidsslmodewas never checked. (Validate sslmode and gssencmode at parse time and in the constructor #47, thanks @PingoLee)connect_timeoutbounds the whole connection attempt, as libpq's does: the TCP dial, TLS or GSS negotiation, startup, authentication and session setup. A server that accepts the connection and then stalls no longer blocksPostgres.Connection, areconnect=truereconnect, a pool checkout orcancel_query!forever. A timeout throwsPostgres.Error("timeout expired while connecting to host:port")where it used to throw Reseau'sOpErrororTLSHandshakeTimeoutError. Authentication now counts toward the window, so a very smallconnect_timeoutcan cut off a slow SCRAM or GSS exchange. Aconnect_timeoutof 0 or less means no limit. (Bound the whole connection attempt by connect_timeout #48)🤖 Generated with Claude Code