npgsql

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 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 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 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 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.

The first beta version of Npgsql 3.1.0 is out and 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. It includes some breakage documented in the migration notes and should be tested carefully.

Please try it out and let you know how it works for you! Release highlights are below, the documentation isn't yet up to date on everything.

• CoreCLR support (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 (document)
• 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.

Npgsql 3.0.7 is out and available at nuget.org.

This release undoes change #946, which made it illegal to start parameter names with digits. While this fixed an SQL parsing issue, it causes too much breakage for ORMs and existing code which uses parameter names such as @1. An alternative fix, #1056, has been applied instead in 3.0.7 - you can use parameter names with digits as before.

(May 6) Setup_NpgsqlDdexProvider.exe added.

Npgsql 3.0.6 is out and available at nuget.org.

This release fixes numerous bugs, including one that could cause pooled connections to "leak" under certain load conditions (#1019). Thanks to @shortspider for raising and fixing the issue.

An additional issue related to Npgsql's internal query parser was fixed (#946). Note that as a result, parameter names can no longer start with a digit - this could cause breakage if you were using parameter names such as :1.

Is is strongly recommended that everyone upgrade. The full list of changes is available here.

(May 6) Setup_NpgsqlDdexProvider.exe added.

Npgsql 3.0.5 is out and available at nuget.org.

This release that could affect users setting MinPoolSize > 1. See issue #918.

Also, when closing a pooled connection that had an active transaction, that transaction would not be rolled back immediately. This could cause issues and has been fixed - transactions are rolled back immediately upon close. See issue #927.

Note that NpgsqlConnection's DataSource property now returns a URL (e.g. tcp://localhost:5432). Code that relied on the contents of DataSource is probably now broken. See issue #903.

Npgsql 2.2 had a Windows installer that would set up Npgsql in the GAC and update your machine.config file - this installer has been revived and will now be released with 3.x version (check our releases tab on Github. Note that in most use cases, Npgsql should not be installed into the GAC - use Nuget instead. See the installation page for more details.

Is is strongly recommended that everyone upgrade. The full list of changes is available here.

Happy new year 2016!

(Jan 9) Setup_NpgsqlDdexProvider.exe added.
(Apr 8) Npgsql-3.0.5_20160408.msi added. Fix #963

Npgsql 3.0.4 is out and available at nuget.org.

This release fixes some important bugs reported since 3.0.3 came out.

In addition, a new SQL Logging feature has been implemented, feel free to read the documentation.

Is is recommended that everyone upgrade.

The full list of changes is available here.

(Dec 30) Setup_NpgsqlDdexProvider.exe added.

Npgsql 3.0.3 is out and available at nuget.org.

This release fixes some important bugs reported since 3.0.2 came out. Is is recommended that everyone upgrade.

The full list of changes is available here.

Npgsql 2.2.7 is out and available at nuget.org.

This is a maintenance release for the 2.x branch which fixes a bug when creating a database with Entity Framework 6. Note that this bug has already been fixed in the 3.x branch.

The 2.x is considered obsolete and will only be maintained to fix critical bugs. You are encouraged to (cautiously!) upgrade to 3.x as soon as possible.

(Dec 30) Setup_Npgsql-2.2.7.0-net40.exe and Setup_Npgsql-2.2.7.0-net45.exe added.

Npgsql 3.0.2 is out and available at nuget.org.

This release fixes some important bugs reported since 3.0.1 came out, and resolves some compatibility issues with Npgsql 2.x. Is is recommended that everyone upgrade.

The full list of changes is available here.

Npgsql 2.2.6 is out and available at nuget.org.

This is a maintenance release for the 2.x branch which fixes some bugs, including a potential SQL injection issue when using citext or other exotic types (see #734). Note that this bug doesn't affect the 3.x branch and there's no need to upgrade.

The 2.x is considered obsolete and will only be maintained to fix critical bugs. You are encouraged to (cautiously!) upgrade to 3.x as soon as possible.

The full list of changes is available here.

Npgsql 3.0.1 is out and available at nuget.org.

This release fixes some bugs reported since 3.0.0 came out, and adds some trivial missing features. Is is recommended that everyone upgrade.

The full list of changes is available here.

Npgsql 3.0.0 is out and available at nuget.org.

Npgsql 3.0.0 is a near-total rewrite, and represents over a year's effort.

• Switch to 100% binary communication with PostgreSQL #447. This has the following advantages:
  • Significant speed increase for some types
  • Improves general stability and removed dependency user-defined parameters such as
    DateStyle, extra_float_digits, lc_monetary etc. (see #514, #324, #163, etc.)
  • More consistent behavior between simple and prepared statements
  • Simplified codebase (we previously supported both text and binary codecs for most types)
• True async support for NpgsqlReader for better scalability. This implements the new .NET 4.5 ADO.NET async methods, except for the async connection methods (these are a major goal for 3.1, see #379.
• Reworked type handing that greatly reduces memory churn. Except your application to allocate and release much less memory than before.
• New high-performance import/export API that exposes PostgreSQL COPY. See the docs for more details.
• Much better support for PostgreSQL asynchronous operations, such as LISTEN/NOTIFY. See the docs for more details.

There are many other changes, see here to get an idea.

Note that Npgsql 3.0 is not a simple drop-in replacement for 2.2: there are some breaking changes involved.
Please consult the migration guide and test extensively before deploying to production.

Major goals for Npgsql 3.1 includes:

• Complete async support for connections (#379)
• Fully implement the Entity Framework 7 provider (already in progress, #249)
• Support .NET Core (#471)
• Full, native PostGIS support (#529)

Please try it out and let us know immediately of any issues!

Npgsql 2.2.5 has just been released and is available via nuget.

This is an important bugfix release, everyone should upgrade. Particularly important is a leak due to an EntityFramework issue (#505), thanks @havard.

This release also includes several changes to make Npgsql work well with Amazon Redshift. Support isn't perfect yet but should be considerably better than before, please report any further issues.

The full list of fixes can be found here.

Note: 2.2.5.0-r2 setups use Npgsql DLL files from official release. 2.2.5.0 doesn't.
Note: 2.2.5.0-r3 setups register Mono.Security.dll to GAC correctly. 2.2.5.0-r2 doesn't.

This is the same as 2.2.4.1. The only change is the assembly versions which were updated to 2.2.4.3. Previously they had the value of 2.2.4 only.

If 2.2.4.1 is working ok for you, you don't need to install these. Except if you are having problems with EntityFramework wizard as reported here #479 . In this case, get the Setup installer and follow the instructions in the issue.

Npgsql 2.2.4.1 has just been released and is available via nuget.

This is a small bugfix-only release which corrects an important Entity Framework issue (#461).

Npgsql 2.2.3 has just been released and is available via nuget.

This is a bugfix-only release which corrects a critical memory leak issue in 2.2.2. Users of 2.2.2 should upgrade to 2.2.3 immediately. See the fix list here.