2 years ago
I'm currently moving from the base postgres template to the timescale version (for financial data) "https://github.com/railwayapp-templates/timescale-postgis-ssl/pkgs/container/timescale-postgis-ssl"
How can I most efficiently and effectively move my data from the old db service to the new?
27 Replies
2 years ago
how much data is in the old database?
2 years ago
id just do pg_dump and pg_restore
2 years ago
i wouldn't mess with the volume, we cant help with data loss
Is The TimescaleDB template I'm going with (i see your a dev on it) the best approach to getting a postgres db with timescale extension/capabilities?
Or is there simple way to just add timescale extension to the existing "atlas_core_db" db
2 years ago
the new database is gonna be the way, installing extensions on dockerized databases isnt the easiest thing
2 years ago
no no i work for railway, theres no need for tips
Much respect. Quick question, I noticed you have "NO_TS_TUNE" set to true.
Given that I have 1 table that will use the timescale timeseries functionality (hyper table / compression and the like), should this be set to false?
2 years ago
i genuinely dont know, sorry
2 years ago
with an sql query that changes that setting, i dont know it off the top of my head
Gotcha, i was able to run it (i can track it down if need be) but it says I need to restart the database
2 years ago
yeah, click restart

