Hello,
We would like to migrate from Heroku to fly.io.
The pros of fly.io are that we can use Warsaw region to handle our customers and the pricing looks good. I did initial configuration with postgres cluster and app works very well for now.
But not sure how much effort it will need from us to maintain this regarding the postgres.
On heroku it’s fire and forget - no problems since 4 years - we just do code and push to github - everything works well (but is expensive) no devops knowledge needed.
On Fly.io In two places you differentiate this:
- First Place:
- We won’t upgrade your Postgres cluster to a new version automatically. You can run
fly image update
to get the latest available point release - We won’t apply security patches to running clusters
(source link to post)
- Second Place:
Upgrading Postgres versions & security patches - Fly.io provides tools likefly image update
to upgrade your database instances to new minor versions of Postgres, but you’ll have to run the upgrades yourself. Same for security patches: you’ll have to apply those to running Postgres clusters.
(source link to post)
You differentiate those two things:
-
using
fly image update
for updating version of Postgres -
“applying security patches to running Postgres clusters”
If I understand correctly It looks applying security patches is different thing than running fly image update
- does it mean login to working cluster machine and do some kind of updating linux machine or do updates in fly.toml files and re-deploying ?
How to apply security patch to running Postgres cluster? Is it related to any kind of downtime ?