Npgsql 11.0 Release Notes
Npgsql 11.0.0 is available on NuGet.
See the 11.0.0 milestone for the full list of issues.
Breaking changes
Dependency injection is now part of Npgsql
The Npgsql.DependencyInjection package was merged into Npgsql. Remove the separate package reference when upgrading. Existing calls to AddNpgsqlDataSource() and related methods continue to work from the Microsoft.Extensions.DependencyInjection namespace, except for previously obsolete overloads, which have been removed. See dependency injection setup (#6594).
Removed multiplexing
The experimental multiplexing mode has been removed. It could increase throughput for some workloads but did not scale well with high concurrency on machines with many CPU cores. Remove Multiplexing and Write Coalescing Buffer Threshold Bytes from your connection strings, even if multiplexing was disabled, and remove any assignments to the corresponding connection string builder properties. Regular connection pooling is unchanged (#6457).
Removed deprecated large object APIs
NpgsqlLargeObjectManager and NpgsqlLargeObjectStream, obsolete since Npgsql 8.0, have been removed. Use PostgreSQL's large object functions directly. For example, lo_get and lo_put read and write byte ranges. If you use lo_open to obtain a descriptor, use it on the same connection and within the same transaction. Existing large objects do not need to be migrated (#6493).
Application Name can change pool metric labels
If you set Application Name in your connection string without explicitly naming the data source, Npgsql 11 uses that application name rather than the connection string as the db.client.connection.pool.name metric tag. Update dashboards that filter on the old label, or set NpgsqlDataSourceBuilder.Name explicitly to control the label and distinguish pools with the same application name. See metrics (#6533).