Skip to content
Compare
Choose a tag to compare

6.0.6 contains three bug fixes, notably for #4582, fixing support for extension types in non-default schemas.

The full list of changes is available here.

Compare
Choose a tag to compare

Fixes backported:

  • Deadlock/hung at NpgsqlDataReader.Cleanup (#4465)

This release also brings VS2022 support to the Npgsql VSIX (which is otherwise discontinued).

Compare
Choose a tag to compare

6.0.5 contains is 7 fixes, everyone is strongly encouraged to upgrade.

The full list of changes is available here.

Compare
Choose a tag to compare

Fixes backported:

  • A connector might be returned twice to the pool if broken while opening new connector (#4479)
  • Deadlock/hung at NpgsqlDataReader.Cleanup (#4465)
Compare
Choose a tag to compare

Fixes backported:

  • Deadlock/hung at NpgsqlDataReader.Cleanup (#4465)
  • NpgsqlDataReader.GetTextReader always returns a reader with UTF8 encoding (#4384)
  • Throw if additional unencrypted bytes are left after SSL negotiation (#4130)
Compare
Choose a tag to compare

6.0.4 contains is the first patch release in a while, and so contains 22 bug fixes. Everyone is strongly encouraged to upgrade.

The full list of changes is available here.

Compare
Choose a tag to compare

Fixes backported:

  • DeadlockDetected returns false by PostgresException.IsTransient (#4409)
  • NpgsqlDataReader.ExecuteScalar doesn't always throw PostgresException (#4378)
  • Intermittent "Unknown message code: X" exceptions. affects 5.X and 6.x (#4305)
  • NpgsqlDataReader.GetTextReader always returns a reader with UTF8 encoding (#4384)
  • Idle connection pruning becomes permanently disbled afrer postgres server restart (same as #4193) (#4373)
Compare
Choose a tag to compare

5.0.12 fixes the following:

  • Fix pruning enable/disable race condition (#4255)
  • Allow flushing of NpgsqlReadBuffer.Stream (#4122)
Compare
Choose a tag to compare

6.0.3 contains important bug fixes, everyone is strongly encouraged to upgrade.

The full list of changes is available here.

Compare
Choose a tag to compare

6.0.0 changed Npgsql's parameter name matching to be case-sensitive; unfortunately, in some specific scenarios this could cause the parameter placeholder to be evaluated as a column name by PostgreSQL, potentially leading to data loss. 6.0.2 reverts this changes and switches back to case-insensitive parameter name matching.

The full list of changes is available here.