Repository navigation
Bump version to 2.6.0 - #46
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 the Nov 5 fixes to users: #42 (closes #41), #45 (fixes #44) and #33.
Bumps the version to 2.6.0. It is a minor release because
validate_dsnis new public API. Included since 2.5.0:Added
Postgres.validate_dsn(dsn)returnsnothingfor a connection string thatparse_dsnaccepts. Otherwise it returns aPostgres.ConnectionParameterErrorwith the failing parameter (key), areason(:unknown_key,:invalid_value,:unsupported_ignoredor:malformed) and the messageparse_dsnwould throw, so a caller no longer has to match on error text. It is public but not exported. (Add validate_dsn for structured connection-parameter errors #33)Fixed
DBInterface.close!now sends the protocol's Terminate message before it closes the socket, as libpq does. The server no longer logs "unexpected EOF on client connection" when a connection is closed normally. (Send Terminate before closing a connection #42)Postgres.cancel_query!now cancels a statement after anInterruptExceptionclosed the connection while that statement ran. It used to throw "cannot cancel query: connection not open", and the statement kept running on the server. On a connection closed withclose!, it now sends a request that the server ignores instead of throwing. (Let cancel_query! cancel a statement after an interrupt closed the socket #45)🤖 Generated with Claude Code