Simple Q: How to move volume to new db service.
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?
17 Replies
Project ID:
N/Ahow much data is in the old database?
Not much
Let me check
TimescaleDB is the new.
looks like 1.5GB
id just do pg_dump and pg_restore
i wouldn't mess with the volume, we cant help with data loss
Gotcha I'll pg_dump and pg_restore. Quick question
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
the new database is gonna be the way, installing extensions on dockerized databases isnt the easiest thing
Gotcha thank you sir
You guys got a tip jar? I'd like to buy you a coffee
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?
Last question haha
i genuinely dont know, sorry
No worries. Hey one quick thing
If I wanted to change a variable in the "postgresql.conf" file
simply max_locks_per_transaction = 128, how could I do this?
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
That wouldn't be a redeploy correct?
Is there a way to just 'reboot' lol
yeah, click restart
(BTW thank you so much for your time and help, you wizard)
gotcha thanks