Install
.NET CLI
dotnet add package Npgsql.EntityFrameworkCore.PostgreSQL --version 1.0.2
Package Manager Console
Install-Package Npgsql.EntityFrameworkCore.PostgreSQL -Version 1.0.2
PackageReference
<PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL" Version="1.0.2" />
Frameworks
Dependencies
Microsoft.EntityFrameworkCore
[1.0.1, )
.NETFramework4.5.1
Microsoft.EntityFrameworkCore.Relational
[1.0.1, )
.NETFramework4.5.1
Microsoft.Extensions.DependencyInjection.Abstractions
[1.0.0, )
.NETFramework4.5.1
Microsoft.Extensions.DependencyInjection
[1.0.0, )
.NETFramework4.5.1
Npgsql
[3.1.8, )
.NETFramework4.5.1
Microsoft.EntityFrameworkCore
[1.0.1, )
.NETStandard1.3
Microsoft.EntityFrameworkCore.Relational
[1.0.1, )
.NETStandard1.3
Microsoft.Extensions.DependencyInjection.Abstractions
[1.0.0, )
.NETStandard1.3
Microsoft.Extensions.DependencyInjection
[1.0.0, )
.NETStandard1.3
Npgsql
[3.1.8, )
.NETStandard1.3
Adoption guide
Teams using PostgreSQL features such as JSONB, arrays or advanced indexing patterns.
Why it appears in the guide: EF Core provider for PostgreSQL with strong support for PostgreSQL-specific capabilities. Trade-off: Provider-specific behavior and SQL translation should be validated when porting from SQL Server-centric models.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.