Postgres could not resize shared memory segment
This comes up when trying to run VACUUM on some of our tables, so far its not a big deal but could become in the future.
The fix is to increase shared memory size limit for the postgres container.
Wondering if anyone else has had the same issue, since response from Railway was "we do not allow increasing SHM size".
Project ID: 76e242e9-db08-4279-a677-6c0063fdb9ce
1 Reply
Project ID:
76e242e9-db08-4279-a677-6c0063fdb9ce