@moissela Yep, you can specify a specific image at provision time.
Postgres now has two different configurations options available, so you will need to be conscious about the setup you’re planning to use ahead of time.
Development single-node configuration: fly pg create --image-ref flyio/postgres-standalone:13.
Production-ready HA configuration: fly pg create --image-ref flyio/postgres:13.
The UX for this process isn’t great, but hoping we can get this improved soon!
Not a specific one: we’ve had some trouble migrating majority of our projects from pg12 to pg13 recently.
This task takes us some time that we need to plan so we can handle correctly and with the right level of attention.
So we need to know that we can start a new postgres instance on Fly with the version (at least the major one) we need in that moment and not be forced with a newly version.
Maybe when we’ll migrate to the Fly platform will also be an opportunity to adopt pg14
So we need to know that we can start a new postgres instance on Fly with the version (at least the major one) we need in that moment and not be forced with a newly version.
Aha! The --image-ref switch does not work if you specify vm size or volume size switches, or if you use the wizard to pick “custom configuration” instead of one from the list. Looks like I have 13 now