a month 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
5 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
🧵 Postgres database server is crashing after adding timescaledb extension
🧵 Urgent: Database Service Still Down After Plan Upgrade – Need Temporary Unlock
🧵 I ran a recursive query and now there is no more space on device
If you find the answer from one of these, please let us know by solving the thread!
a month ago
---
a month 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 • about 2 months ago
a month 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
a month 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.
a month ago
Thank you so much passos your suggestion helped us to ssh into the container
Status changed to Solved sarahkb125 • about 1 month ago