a month ago
Hi Railway Support,
I’m experiencing what appears to be a bug in Railway’s Database UI for one of my PostgreSQL services.
Project ID: 360b6515-7eeb-45cc-aa83-810c43835c22
Service: pg-hypocaust
Service ID: ea5e6d51-dd99-48d7-81cc-04743b89e608
When I open the pg-hypocaust service in the Railway dashboard, go to Database, the UI displays:
“You have no tables”
This is incorrect. The PostgreSQL database is an active production database and my production application is currently using it successfully. The application is able to read/write the data, so I know the database and tables exist and are accessible.
For comparison, I have another PostgreSQL service in the same project, pg-atrium, and its Database tab correctly displays its tables. The problem appears to be specific to pg-hypocaust.
I also had the Railway agent investigate this. It confirmed that:
pg-hypocaustis online and running normally.- The PostgreSQL data directory exists and has the expected PostgreSQL structure.
- The database files/data are present on the mounted volume.
- The service has been running in production.
- The “no tables” message is coming specifically from Railway's Database tab.
The agent therefore concluded that the most likely issue is that Railway's dashboard is failing to enumerate the tables for this database, rather than the tables actually being absent.
I am not looking for help verifying whether the tables exist — the production application itself is already successfully using them. I’d like you to investigate why Railway’s Database UI cannot discover/display them.
Could you please:
- Investigate the table discovery/enumeration for
pg-hypocaust. - Confirm whether this is a Railway dashboard/platform bug.
- Fix or refresh whatever metadata/discovery mechanism is responsible, if possible.
- Let me know whether there is anything I need to do on my side.
Additionally, I originally spent agentic analysis credits investigating this issue because I reasonably expected the Railway agent to be able to diagnose or escalate a Railway platform problem. If this is confirmed to be a Railway-side bug, I would appreciate it if you could consider a credit/refund for the agentic usage incurred while investigating it, or let me know which billing/support process I should follow for that.
Thanks!
2 Replies
a month ago
Also, I upgraded to Pro to open a private thread, but then I couldn't because I was bounced back and forth between my private thread creation dialog and a dialog telling me I need to acknowledge that this thread may be made public. I clicked accept and instead of the private thread opening, I was just bounced back.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
The Database tab reads only the single database named by your service's PGDATABASE / POSTGRES_DB variable, queried live from information_schema on each load. If your application's connection string connects to a different database on the same Postgres instance (a common case is a URL ending at the port with no database path, which defaults to the connecting username), your tables live in that database while the tab is looking at another one, producing the "You have no tables" message. Compare the database name in the connection string your app actually uses against the value of PGDATABASE on pg-hypocaust. pg-atrium displaying its tables correctly just means its app and its variable happen to agree on the database name. Regarding the agent credits, you willingly used the AI Assistant, which means you're responsible for the outcomes, billing or otherwise, and we don't refund usage that came from actions you initiated through the assistant. On the private-thread creation dialog looping, we're sorry for the friction there.
Status changed to Awaiting User Response Railway • 25 days ago
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago