21 days ago
Hi Railway team, I'd like to enable wal_level=logical on the Postgres service in project "Latcom-dynamic-spontaneity" (project id 40d6280d-0e95-4f97-b9e3-da837f85052c) so we can set up native logical replication to a DR replica (DigitalOcean Managed Postgres).
ALTER SYSTEM SET wal_level='logical' returns success but pending_restart stays false and the setting reverts to 'replica' on next check looks
like the image overrides postgresql.auto.conf externally.
Could you flip wal_level to 'logical' on this PG service and trigger a restart? max_wal_senders=10 and max_replication_slots=10 are already
adequate, so no other changes needed.
This is for a payments platform (~200K txn/mo target) we currently
fall back to hourly snapshot replication for DR, but logical replication would cut RPO from ~1h to seconds.
Thanks,
Richard Mas
1 Replies
21 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 Railway • 21 days ago
21 days ago
Hey, unfortunately Railway can't change the PostgreSQL configuration, but you can do it by using the Railway CLI (via SSH).
1. First, install the CLI by following the guide: https://docs.railway.com/cli#installing-the-cli.
2. After installing, type railway link and follow the procedures to link the CLI to your PostgreSQL database/service.
3. Then, use railway ssh to open a shell on your database. Navigate to /var/lib/postgresql/data to find the configuration file to make the necessary changes. You may need to install a terminal text editor such as nano or vi for editing it.
Let me know if you have any issues while following the steps above.