PG volume not showing as full, but PG having no space on disc

jackrkelly
PRO

2 months ago

2025-06-16 19:14:03.454 UTC [14215] ERROR: could not resize shared memory segment "/PostgreSQL.361173462" to 4194304 bytes: No space left on device

Solved

5 Replies

jackrkelly
PRO

2 months ago

Screenshots


jackrkelly
PRO

2 months ago

The error is about shared memory, not disk space actually*


jackrkelly
PRO

2 months ago

We're hitting a wall with our Postgres database in production. Getting this error when running complex queries:

ERROR: could not resize shared memory segment "/PostgreSQL.361173462" to 4194304 bytes: No space left on device

Did some digging and found out our /dev/shm is only 62MB, which isn't enough for PostgreSQL's parallel workers. We've got about 37 active connections and when Postgres tries to spin up parallel workers for bigger queries, it just dies.

Is there any way to bump up the shared memory limit? Even getting it to 512MB would be huge. This is hitting us pretty hard in production right now, so any help would be amazing. Happy to provide more details or try any workarounds you might suggest.

Thanks!


jackrkelly
PRO

2 months ago

am seeing the docs now, regarding this issue, apologies I missed it. https://docs.railway.com/guides/postgresql


2 months ago

All good! The issue with our Postgres that throws people off is that, it's not managed, however, it's so easy to deploy Postgres on Railway, people think that it is!

I am happy that you found a resolution to your problem. Here if you need any more help.

Thanks,
Angelo


Status changed to Awaiting User Response Railway about 2 months ago


Status changed to Solved jackrkelly about 2 months ago