Railway doesn't have native connection pooling for Postgres today. Without it, your database can quickly run out of connections as your app scales — and the workarounds are too manual.

We're adding one-click PgBouncer connection pooling that works on any Postgres setup, including high-availability clusters. Enabling or disabling pooling won't restart your database. You'll get a pooled DATABASE_URL by default (transaction mode) plus an unpooled DATABASE_UNPOOLED_URL for operations that need a direct connection like migrations, LISTEN/NOTIFY, and CREATE INDEX CONCURRENTLY. Pool mode is selectable (transaction, session, or statement) and changeable anytime without touching your database.

What connection pooling features matter most to you? Drop a comment!