The guest explained why his team could not just pre-build a container image for every mix of Postgres extensions. Usage data showed nearly every extension gets pulled and no two users pick the same set, so they built a registry that composes images on demand.
Exactly.
Not far from that. Exactly.
…that solves the problem both for Kubernetes and non-Kubernetes environment. So this also solves the problem for Docker, right? Or Podman or any tool you use to run containers. And so the idea is what you were saying, Nikolai. So we thought about, hold on, what if we pre-generate the container images? And so now we have the data and we see what extensions people use. And it's interesting because out of these 225 extensions, almost all are pulled at some point. Of course, there is more popular than others, but it's not like, oh, there's 10 and nobody else uses this one. No, no, no. They're all pulled. They're all used. And some users use one, two extensions, or they use 10, or they use 15. But among those that use 10, they're different subsets. Everybody uses a different combination. So if we think about the math to compute all possible combinations of…
Also, there is also like a variety of versions.
And actually, yes, we have now a system that allows you to build this and explores or explores even more the cardinality because we give you even more options to decide what you want. So what's the end goal? The end goal is to have an image that contains what you want and nothing else. That's…
All right. So here's the good news is that that's awesome. And it brings in these extensions, but I doubt it installs all those extensions into Postgres for you. I bet it only puts them out there so that when the database needs them or wants to see them, it can go ahead and add those extensions.