deps(deps): bump pgwire from 0.40.7 to 0.41.0

[dependabot]

Bumps pgwire from 0.40.7 to 0.41.0.

Release notes

Sourced from pgwire's releases.

v0.41.0

What's Changed

• feat: client api secret key and cancel support by @​sunng87 in sunng87/pgwire#456
• feat: protocol negotiation by @​sunng87 in sunng87/pgwire#457
• chore(deps): update pg_interval requirement from 0.5 to 0.6 by @​dependabot[bot] in sunng87/pgwire#444
• test: integration tests for client API against real PostgreSQL by @​sunng87 in sunng87/pgwire#458
• feat: client transaction status tracking by @​sunng87 in sunng87/pgwire#459
• chore(deps): update gluesql requirement from 0.19 to 0.20 by @​dependabot[bot] in sunng87/pgwire#460
• feat: empty statement implementation for server-api by @​sunng87 in sunng87/pgwire#461

Full Changelog: sunng87/pgwire@v0.40.7...v0.41.0

Changelog

Sourced from pgwire's changelog.

[0.41.0] - 2026-09-04

Added

• Client API: transaction status tracking. ClientInfo::transaction_status reports the status carried by the last ReadyForQuery message (idle, in transaction, or in a failed transaction), updated automatically on every code path: startup, simple and extended query, and the error-recovery drains.
• Client API: protocol version negotiation. Config::protocol_version selects the version to advertise in the startup message, defaulting to 3.0. Following libpq, a test version 3.9999 is available to request the newest minor version a server supports: the client handles the server's NegotiateProtocolVersion response (both the full 32-bit version form used by PostgreSQL 18+ and the minor-only form used by older servers) and adopts the negotiated version for the rest of the connection.

Changed

• Breaking: QueryParser::parse_sql now returns PgWireResult<Option<Self::Statement>>, and StoredStatement::parse correspondingly returns Option<StoredStatement<S>>. None denotes an empty query: it is stored as an empty statement and executes to EmptyQueryResponse. This allows a query parser to report its own notion of empty query; syntactically empty queries (semicolons and whitespace only) are still never passed to the parser.
• Breaking: PortalStore now represents empty statements and portals. get_statement returns Option<Entry<StoredStatement<S>>> and get_portal returns Option<Entry<Portal<S>>>: the new Entry::Empty variant marks a name under which an empty prepared statement or portal is stored, alongside the new put_empty_statement/put_empty_portal methods. Like every put_*, storing an empty entry replaces whatever was previously stored under that name, and rm_*/clear_portals remove empty entries along with regular ones. StoredStatement and Portal themselves are unchanged — the impact is limited to PortalStore implementors and code calling get_statement/get_portal directly (Entry::value helps with the migration).
• Updated pg_interval to 0.6

Fixed

• Extended query protocol: empty queries (a query string without any statement, such as "" or ";;") are now handled like PostgreSQL instead of being dispatched to the query parser: Parse succeeds without calling QueryParser and stores an empty statement, Describe answers ParameterDescription (no parameters) + NoData, Bind succeeds (rejecting bound parameters with 08P01) and stores an empty portal, and Execute returns EmptyQueryResponse without reaching do_query. An empty Parse replaces any statement previously stored under the same name, and Close/Sync drop empty statements and the unnamed empty

... (truncated)

Commits

• 1e62dff chore: Release
• 6b59c92 docs: update readme status
• b41414f feat: empty statement implementation for server-api (#461)
• c438ac2 lint: cargo toml
• 2cb0014 chore(deps): update gluesql requirement from 0.19 to 0.20 (#460)
• 623ccc2 feat: client transaction status tracking (#459)
• 8f2ccf1 test: integration tests for client API against real PostgreSQL (#458)
• b706061 chore(deps): update pg_interval requirement from 0.5 to 0.6 (#444)
• b2ee579 feat: protocol negotiation (#457)
• bdc81f6 feat: client api secret key and cancel support (#456)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)