today, CNPG provides two operand container images: postgresql-containers and postgis-containers based on two respective upstream containers maintained by the docker community.

there are already several requests for specific extensions, and i'm sure more will come. i would propose that CNPG changes its strategy to simply provide two images: a "minimal" image with only the bare minimum extensions which is suitable for users to fork and customize with their own list of extensions, and a "standard" image with a liberal policy of including any extension which is packaged for Debian by CNPG.

this policy would encourage contribution to Postgres Debian packaging as an upstream (if desired extensions aren't there already), consolidate maintenance in the debian ecosystem, provide an easy way for CNPG users to get an image with most extensions they want, and still provide a minimal small image as a base for customization.

i don't think there needs to be a separate image for postgis; i think it can be included in a standard image (similar to what cloud providers do). at some point in the future there may be concerns about the size getting too bloated, but i think we can cross that bridge when we come to it (and discuss whether there should be some third middle option). in the meantime if we only add extensions that are explicitly requested by a user and available in Debian repos, then i think the pace of growth will be manageable.

thoughts?