migrating DB plugin to service - timescaledb
I've got some old postgres plugins i need to migrate.
When testing my backups locally i see i need to have timescaledb installed for the restore to work. Making this work on my machine is another issue but on this post my question is:
Will this raise issues when using the auto-migrate tool for DB plugin to service? Or is this already taken into consideration by the migration template?
13 Replies
Project ID:
N/AN/A
I think the migration tool will always deploy a new database with timescale for backwards compatibility
and what about postgresql version?
the plugin is on pg13
i believe :latest is pg16
it will be a new version, I think it's pg 15
ok
but data will be copied
for transparency the migration does not deploy the same database that adding a new database to your project manually does
ok
data is copied from the plugin to the new database, there is extremely low risk of data loss since all connected services are stopped and the old database is never deleted automatically
"rollback" would basically be reseting reference ENV variables ?
although, it's the weekend, if you do end up needing support from the team it won't be available until a workday
yes that should be how it works
my apps have very low traffic on the weekends and more load during the week so i try to do this kind of work on weekends to avoid disruption to the users 😅
fair enough