.NET Data Provider for PostgreSQL

About Npgsql

Npgsql is the .NET data provider for PostgreSQL. It allows any program developed for .NET framework to access a PostgreSQL database server. It is implemented in 100% C# code. PostgreSQL versions since 9.0 are officially supported, others may work. Read more...

Latest News

  • Npgsql 3.1.6 and Npgsql EF6 3.1.1 are out

    Npgsql 3.1.6 and the Entity Framework Core 3.1.6 have been released and are available on

    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.

    EF6.Npgsql 3.1.1 is a fix for #27, which broke some complex queries (mainly inheritance-related).

  • Npgsql 3.1.5 and Npgsql EFCore 1.0.0 are out

    Npgsql 3.1.5 and the Entity Framework Core 1.0.0 have been released and are available on

    Both versions target .NET Core RTM (1.0.0), which was released a few days ago. This is the EFCore provider’s first stable release, although it probably hasn’t been battle-tested yet - please report all issues on the EFCore provider repo. To get started, follow the instructions in the EFCore docs. You can also find some info on Npgsql-specific features and unsupported features on the Npgsql EFCore page.

    The complete list of issues for Npgsql 3.1.5 is here.

  • Npgsql 3.1.4 and 3.0.8

    Npgsql 3.1.4 and 3.0.8 have been released and are available on

    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.

    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.

    Also, I’m away on a pretty intensive 5-month and won’t be able to invest as much time in Npgsql as I could recently. I’ll do my best to solve bugs but work on 3.2 probably won’t start before November. Please be patient :)

    The complete list of issues for 3.1.4 is here. 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

    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 Entity Framework 6 Provider 3.1.0

    Npgsql’s Entity Framework 6 (and 5) provider version 3.1.0 has been released and is available on This allows use of the newly-released Npgsql 3.1.0 with Entity Framework 6/5.

    Starting now, EF6/5 provider releases will be decoupled from Npgsql itself; up to now every time a version bump occured on Npgsql, an EF6/5 provider with the same version released. From now on each project will follow its own versioning.

Click here for older announcements