Skip to content

v4.7.3

Latest

Choose a tag to compare

@lahma lahma released this 09 Nov 14:49

One fix for the 4.7 line. There is no public API change and no schema change.

Fixed

  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or cluster check-in commit now goes through its commit validator and transient retry as on other databases, scheduler listeners hear of the failure, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412 for the report and analysis. (#4262, from #4258, #4255)

Compatibility

EnlistConnection refuses a transaction that has ended (committed, rolled back or disposed) with that reason before checking that it belongs to the connection. A committed SQL Server transaction used to be refused as belonging to a different connection. The exception type and parameter name are unchanged.

What's Changed

Fixes

  • 4.7.3: a transaction its driver has disposed counts as ended, so a failed commit on Npgsql is reported as itself by @lahma in #4262

Full Changelog: v4.7.2...v4.7.3