Tune Engine Settings From a New Parameters Tab
Change supported settings on a single database, cache or queue from its own page, live where the engine allows it, and PostgreSQL parameter group changes now reach running databases when you save them.
What's changed
- A Parameters tab on PostgreSQL, MySQL and MariaDB databases, Redis, Valkey and Dragonfly caches and RabbitMQ queues shows the group in use, its saved values and the settings you can change
- Settings the engine can reload apply to the running instance without a restart; where a setting needs one, you confirm a separate restart first
- Each save creates a parameter group for that instance only, so other instances on the same group keep their settings
- Saving a PostgreSQL parameter group applies it to every running database that uses it when all changed settings can reload, touching only those settings; otherwise the save lists what waits for each database's next update
- PostgreSQL groups list what can be set, what applies without a restart and what the platform manages, and a misspelled setting name is refused with a suggestion
- PostgreSQL groups accept archive_timeout from 60 seconds to 1 hour, and write-ahead log settings are checked against their allowed ranges when you save
- Supported RabbitMQ settings in a queue's parameter group now take effect, and the database Edit page tells you when switching groups keeps the database running