16 days ago
Hey all, I’m new to Railway and trying to understand the intended workflow for Postgres logs.
Project ID: 861b88dd-e16b-4ed5-91c3-ef1f0937bbad
My Railway Postgres service is healthy and active, but normal Postgres startup lines are showing as red/error in the log UI, for example:
LOG: starting PostgreSQL and LOG: listening on IPv4 address and LOG: database system is ready to accept connections
These seem like normal Postgres LOG: messages, not actual errors. I also disabled checkpoint logging with ALTER SYSTEM SET log_checkpoints = off, which helped reduce noise, but startup/info-level Postgres messages still appear red.
I’m using the Railway Postgres template image:
ghcr.io/railwayapp-templates/postgres-ssl:17
Is there a recommended way to make Railway log colors/severity match the actual Postgres log level? Or is this expected because Postgres writes normal logs to stderr?
Mostly I’m trying to find a clean way to review DB health/log overviews without having to open every red line to figure out whether it’s a real issue or just normal Postgres output.
Also saw this on startup:
collation-refresh: psql: error: /tmp/collation-refresh....sql: Permission denied
DB still starts fine, but not sure if that line matters.
Thanks, appreciate any guidance.
4 Replies
16 days ago
Postgres outputs logs to stderr (errors) by default
Thank you, I saw that online somewhere. I was hoping someone had an easy workaround or something because it's strange to me that the logs are setup this way. My project's Python logs make much more sense integrated with Railway Logs with automatic coloring.
13 days ago
This is expected because Postgres writes normal logs to stderr.