Kurdiez
Urgent! Production DB is showing "could not resize shared memory segment" error
I had no idea when you said
Runtime I was supposed to go to the Settings to change that. You never mentioned that that is a settings in Railway... I just understood as some runtime you have that automatically goes into Legacy mode.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
I am really confused now. Do you understand what I've done so far? Because that's exactly what I have already done for
genie-new-db and I tested that that didn't solve the problem.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
You just said that in order for the
RAILWAY_SHM_SIZE_BYTES="536870912" to take an effect in genie-new-db service, I need to also set the same variable RAILWAY_SHM_SIZE_BYTES="536870912" to the genie-db service. That's how I understood.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
Yes and that's why I set the
RAILWAY_SHM_SIZE_BYTES to the service genie-new-db and it's not working. Are you saying both genie-new-db and genie-db services need to have the same RAILWAY_SHM_SIZE_BYTES="536870912" for this to take an effect?34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
What I am saying is we are preparing another new DB to stop using
genie-db. I need to get the new DB called genie-new-db working. And this is the one that ran into exact same memory issue and I set that one to
as you instructed and it's not working. This is the 3rd time I am mentioning this to you.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
I don't think you are understanding what I am saying. I said that whether you say it's not something you support or not, I made that change many months ago and that particular DB
genie-db is our current production DB and its memory issue got solved with the 30GB I set and it works. I'm not gonna bump that down to 500MB when it's serving up live users right now in production.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
genie-new-db is the one that needs to work and that's the one that already has
as you instructed and as I mentioned here (https://discord.com/channels/713503345364697088/1274291514268188811/1274423235470954586) It's not working still34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
On second thought I dont' want to do that to
genie-db (the current PROD) because it's working well and serving live traffic right now. I dont' want to disturb the production.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
Ok, I can also set
RAILWAY_SHM_SIZE_BYTES="536870912" for the current DB genie-db service. But I really need the genie-new-db working. It is a blocker for us move forward in production.34 replies
Urgent! Production DB is showing "could not resize shared memory segment" error
There are two Postgres DB services as you can see. The old one is just called
genie-db and the new one I am migrating to is called genie-new-db. The old one genie-db has no problem allocating memory and works fine but as soon as I use the genie-new-db , I run into the memory allocation issue.
- They both have RAILWAY_SHM_SIZE_BYTES environment variable set.
- The old genie-db is version 15.5 with timescale and PostGIS extensions by default
- The new genie-new-db is version 16.3 without timescale and PostGIS extensions34 replies