Here is the screenshots.

You can check via df -h inside the Postgres that Railway actually mounted the expanded volume. Have you tried that?

They haven't grew their volume to begin with.

That’s odd, I replicated the same thing and it worked for me. The volume was increased.

Then maybe it’s a hobby plan limitation.

They have not attempted to grow their volume at all, they have not even pressed the button.

Ouch . Bro said he increased the space, which I presumed he meant the volume.

Thank you for the answers.
Apparently, I misled you initially. I increased the RAM and CPU that were originally limited for the Postgress node (not DISK space).
A few questions. Please help me understand.

1) I only have a button in Postgres to increase from 500 MB to 250 GB. Why do I need that much? I understand it is a Hobbie plan limitation?

2) Why am I suddenly running out of space for the Postgres node? Although previously 2 months was enough for my several Workflows.

3) How can I remove unnecessary stuff in it, optimize it? And what and how in n8n is taking up space in Postgres?

Screenshot in Settings.

Another one. When I tried to push "Grow" button to resize maximum 500 MB to 1 GB there is an error.

That's likely related to the current outage. Wait to troubleshoot until it's resolved.

And what means 10$ bounty in my topic? I have contacted community support before. There were no rewards for answers.

Railway pays the bounty. Not you.

I see. Thanks. Now the maximum disk space size has increased from 500 MB to 1 GB. But Postgres has such an inscription about pause in deployments. Is it some kind of work on the server?

Guys, tell me please, what I need to do with Postgres in order not to delete my database? In N8N Primary, Work and Redis restarted and deployed after servers fall. Here is the screenshots.

Your database is safe, don’t worry.

I recommend you upgrade to Pro so you can have backups. It’s really important.

Also, try rolling back to the latest version that you remember was working (just go to that deploy and click the rollback button)

You mean last version deploy in Postgress settings?

Can be, but also the primary and worker.

Maybe you know some issues?
Why am I running out of space for the Postgres node? Although previously 2 months was enough for my several Workflows. What does the Postgres database space footprint depend on?

How can I remove unnecessary stuff in it, optimize Postgres database? And what and how in n8n is taking up space in Postgres?

Screen

To reduce postgres size you’ll have to adjust or add some of the following variables:

https://docs.n8n.io/hosting/configuration/environment-variables/executions/

Basically have the data prune enabled and reduce the total time to delete or the number of executions or both.

It works. Thanks for both advices (redeployment previous versions + adding some variables to Postgres.