Gabriele Bartolini

This is the approach we've taken with CloudNativePG: https://cloudnative-pg.io/documentation/current/troubleshooting/#error-while-bootstrapping-the-data-directory

As a CloudNativePG maintainer (CNCF Sandbox project), in-place upgrades are critical for database workloads that use local storage.

My initial (unbinding) proposal is to enable the definition of extension images at the following two layers: - Image Catalog (either global or local in the namespace) - Directly in...

Thanks for your time @theory. > * Does the catalog need a way to specify the default version of an extension when it has multiple versions? This would hand the...

Based on your reply, I would start with a simple approach for now that doesn't consider versions. I have struck through that section above.

> Seems like yet another example of the overall challenge of ABI/API compatibility of extension upgrades. I like the `disableConnectionsIfNotAligned` proposal, though it will have to be aware of what's...

I spoke with @NiccoloFei and @mnencia this morning. We plan to prioritise an initial implementation that only covers the `.spec.postgresql.extension` definition, deferring the image catalog implementation to a later moment,...

# Proposal of configuration control During the call, we also talked about keeping open the possibility to host multiple extensions in a single image. The idea is to propose three...

Worth linking this: https://github.com/kubernetes/enhancements/pull/5450

FYI - We are working on a plugin's interface at the moment (CNPG-I). Although we are currently focusing on backups and recovery, this could be a use case. But ......