Rebooting Postgres Instance
Hi. I've just moved one of my databases from a self-hosted PostgreSQL database to a Railway Postgres instance.
Due to copying quite a large amount of data, my CPU usage and Memory usage spiked for a while (expected), and CPU usage has gone back down for the most part... but memory usage still at ~7.5GB.
I'm guessing that rebooting the Postgres instance would probably lower that memory usage some.
I can't see anything in the panel to reboot my Postgres instance, is there any way to do this?
328a5f9d-67a9-4dd3-a605-143a716f788a7 Replies
Project ID:
328a5f9d-67a9-4dd3-a605-143a716f788aGoing to bump this since it's been a couple of days and not really sure what to do.
Flagging this thread. A team member will be with you shortly.
Adding it to my to-dos to investigate.
Hey there @sohcah - so I think its due to an annoying caching behavior that we don't really give ya the knobs for just yet...
The issue is that Postgres will just expand and take up all the mem availible.
In your case, it sees 8GB and just wants to use it all up after import.
Anyways, just restarted the DB
Lemme know if that helped!
Unfortunately, it’s only reduced it to about 7.3GB. Probably going to consider something like CockroachDB or planetscale for my DB instead…. Might be a better fit anyway due the amount of data
Gotcha, admittedly our DBs are a bit of a weak point on the platform, we have improvements coming here soon.
Will still be keeping my other (less stupidly big) databases on Railway, super hyped to see what’s planned there 🙂 (maybe allow you to select different databases within the UI?)