The total size of the binary is 29.80MB (compared to 14.83MB trimmed, 11.28MB trimmed compressed). Npgsql code accounts for 4.2MB. Inspect actual size within Npgsql to understand what's going on, e.g. where do we have generic explosion.

A lot of this most probably comes from our type handlers, see what can be done there.

Dumps produced by @eerhardt (thank you ❤️):

Npgsql.Internal.TypeHandlers.txt
npgsql-aot-size.txt

Work:

• Introduce NpgsqlSlimDataSourceBuilder #4965
  • Add slim data source builder support to Npgsql.DependencyInjection #5005
• Move the System.Text.Json support to an opt-in type mapping plugin #4846
• Fix generic explosion from MultirangeHandler with native AOT #4892
• Make range/multirange support opt-in #4898
  • Split TypeMapperResolver from TypeHandlerResolver #4973 (remove remaining references to NpgsqlRange)
• Remove geometry type regex parsing logic (removing regex dependency entirely) #4896
• Add NativeAOT binary size report to our CI #4897
• Arrays
  • Reduce AOT size of ArrayHandler #4926
  • Array code bloat reduction  #4961
  • Make arrays opt-in on NpgsqlSlimDataSourceBuilder #4988
• Allow disabling encryption to reduce binary size #4966
• Add a separate resolver for records #4971
• Make geometry, network, internal types opt-in
• ICU?