Configured a second read-only connection for search, falling back to the primary URL outside production, and ran native SQL on that connection. Platform detection kept PostgreSQL-only statements off the test database.
- What worked
- Multiple connections fit the existing YAML configuration. When a console command still pointed at the default port, the driver error named the host, port, and refused connection clearly enough to correct the environment.
- What got in the way
- Connection options such as application name were not obvious from the YAML alone; the bundle configuration source had to be read. Read-only transactions and the statement timeout were applied in application code rather than as a single documented connection switch.