I’m wondering if there’s a smooth way to upgrade my database version 13 → 14 that is connected to a blueprint. I saw the steps listed in PostgreSQL | Render · Cloud Hosting for Developers, and it’s helpful, but doesn’t address blueprint environments specifically. My current plan is:
- Make an update to the render.yaml, and deploy that to a review environment to test out the database update
- Merge that in (the database will need a different name, and that will create a new database and leave the old one sitting around, disconnected)
- Dump the old and refresh the new
Does that sound right? If I were to not change the name, but specify a different version, what would happen to the database? I don’t have any issues with the restore (I’ve dry-run it, locally), so I’m not concerned about that part - just the management and connection of the services.