Npgsql 3.1.8

Npgsql 3.1.8 contains two important deadlock fixes that could occur when performing synchronous operations on the thread pool, one which caused thread pool exhaustion when opening (#1232) and another with multistatement commands (#1256).

In addition, some performance optimizations have been made which should make pooled connection open
work much faster.

The complete list of issues is here.

(Sep 25, 2016) NpgsqlDdexProvider-3.1.0.vsix added

Npgsql 3.1.7

The complete list of issues is here.

Npgsql 3.1.6

Npgsql 3.1.6 is a minor bug release that mainly fixes the incorrect nuget ID accidentally published in 3.1.5
(npgsql instead of Npgsql).

The complete list of issues is here.

Npgsql 3.1.5

Npgsql 3.1.5 targets .NET Core RTM (1.0.0), which was released a few days ago.

The complete list of issues for Npgsql 3.1.5 is here.

Npgsql 3.1.4

Npgsql 3.1.4 mainly fixes some more cases of missing ConfigureAwait(false) which could cause deadlocks, you are strongly encouraged to upgrade, especially if you use the async APIs.

The complete list of issues for 3.1.4 is here.

Npgsql 3.0.8

Npgsql 3.0.8 is an important update in the 3.0.x line. You should definitely upgrade to 3.1.x, but if for
some reason you can't 3.0.8 fixes quite a few bugs.

The complete list of issues for 3.0.8 is here.

Npgsql 3.1.3

Npgsql 3.1.3 has been released and is available on nuget.org.

This release fixes some important issues:

• PostgresException now properly inherits from NpgsqlException (#1117).
• When executing big multistatement commands, ConfigureAwait(false) was missing. This could lead to deadlocks in some cases, even when using synchronous I/O. (#1136).
• Because of the new composite type support in 3.1, initial connections to database with a large number of tables could be very slow. This is now fixed. (#1126).

All users of 3.1.x should upgrade immediately.

The complete list of issues is here.

Npgsql 3.1.2

Npgsql 3.1.2 has been released and is available on nuget.org.

This release fixes a major bug where the read timeout was set incorrectly, resulting in incorrect timeout exceptions.

Also, async calls weren't really executed asynchronously when using SSL (TlsClientStream specifically), this has been resolved and async calls will be truly async.

All users of 3.1.x should upgrade immediately.

Npgsql 3.1.1

Npgsql 3.1.1 has been released and is available on nuget.org.

This releases fixes some minor bugs and removes an embarrassing Console.WriteLine that somehow made it into the final release.

It also implements the new CoreCLR data reader schema API (https://github.com/dotnet/corefx/issues/5915), a better way to discover information about columns you select. It's been made available in .NET Framework as well.

The complete list of issues is here.

Npgsql 3.1.0

Npgsql 3.1.0 has been released and is available on nuget.org.

This version represents 9 months of work since the release of 3.0.0, and is a significant release touching many areas of Npgsql. This version hasn't received an extensive beta testing period and should be used with care, it's recommended to wait for 3.1.1 for critical applications. It includes some breakage documented in the migration notes.

Npgsql release highlights are below, the documentation isn't yet up to date on everything. Please try both Npgsql and the EFCore provider and let you know how they works for you!

• CoreCLR support (rc2, netstandard13). Some known issues will be fixed for 3.1.0 but things should already work pretty well.
• Fixed multi-statement commands issues (#641). You can now send commands with statements that depend on each other, such as "CREATE TABLE X ...; INSERT INTO X..."
• The connection pool has been rewritten from scratch and many previous performance issues should be gone (#726).
• NpgsqlConnection's OpenAsync() is now truly async, (#379) and Open() is now fully sync (#709).
• Native binary support for PostGIS 2D types, thanks @rossini-t (#665).
• Composite type support (#441), see the PostgreSQL docs and the the Npgsql docs.
• Exception behavior has been improved and made more compatible with other ADO.NET providers. It's now easier to catch exceptions Npgsql throws (#897).
• When mapping enum or composite types, you can now control how field names are mapped to PostgreSQL names (#859).
• Continued efforts from 3.0 to reduce heap allocations - Npgsql 3.1 should place even less pressure on the garbage collector.

The complete list of issues is here.

Note that the Entity Framework 6/5 providers, the GAC installer and the DDEX provider will be released later.