Postgres DB crashes due to below issue

tutoxapp
HOBBYOP

25 days ago

the DB was up and running

and we used the below ALTER command to update the postgresql.conf file

ALTERSYSTEMSET shared_preload_libraries = 'auto_explain,pg_stat_statements,pg_stat_kcache';

after we restarted the postgre service it failed with the below error:

2025-10-23 18:47:20.148 UTC [5] FATAL: could not access file "auto_explain,pg_stat_statements,pg_stat_kcache": No such file or directory

2025-10-23 18:47:20.149 UTC [5] LOG: database system is shut down

is there an option to revert the setting on the file postgresql.conf file, so that we can resum the service 

Solved$10 Bounty

5 Replies

tutoxapp
HOBBYOP

25 days ago

---

brody
EMPLOYEE

25 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • 25 days ago

fra
HOBBYTop 10% Contributor

24 days ago

I don't think you can if you don't have a backup (but let's see if other people know more)...

I'm not sure if this is the right thing to do, but maybe you can access to the container vis ssh and update the file manually?
this should be the route: /var/lib/postgresql/data/pgdata/postgresql.conf

fra

I don't think you can if you don't have a backup (but let's see if other people know more)...I'm not sure if this is the right thing to do, but maybe you can access to the container vis ssh and update the file manually?this should be the route: /var/lib/postgresql/data/pgdata/postgresql.conf

passos
MODERATOR

24 days ago

Expanding on this answer, to SSH into the service, you need to ensure that the service deployment remains active. Modify your startup command to sleep 10000000 then install the Railway CLI and SSH into your container. Once connected, remove the changes you made by locating the shared_preload_libraries parameter in the postgresql.conf file and deleting it completely.

After that, remove your current deployment and redeploy it. If you have any questions about any of the steps, feel free to ask for help.

passos

Expanding on this answer, to SSH into the service, you need to ensure that the service deployment remains active. Modify your startup command to sleep 10000000 then install the Railway CLI and SSH into your container. Once connected, remove the changes you made by locating the shared_preload_libraries parameter in the postgresql.conf file and deleting it completely.After that, remove your current deployment and redeploy it. If you have any questions about any of the steps, feel free to ask for help.

tutoxapp
HOBBYOP

24 days ago

Thank you so much passos your suggestion helped us to ssh into the container

Status changed to Solved sarahkb125 • 24 days ago

Loading...
Postgres DB crashes due to below issue - Railway Help Station