Npgsql has its own, custom logging API. While it's satisfactory, it forces users to implement their own adapters every time, and it lacks some nice and standard features.

We tried to use Microsoft.Extensions.Logging in 3.2, but back in the days of .NET Standard 1.x this brought in a huge number of unwanted dependencies which nobody wanted, so we ended up rolling this back (#1438).

We can revisit this. Options are:

• Microsoft.Extensions.Logging
• Take another look at LibLog, which may have fixed the perf issues it had a year ago
• Just keep the current solution, nobody's really complaining