PostgreSQL Settings ​
PostgreSQL Settings tunes the performance and resource parameters of the local PostgreSQL server. Security, authentication, network, and TLS parameters are deliberately not editable here.
Until the PostgreSQL module is installed, the page says so and changes nothing.
Overview ​
URL: /admin/settings/postgresql-settings
The page appears under Settings > Databases.
Configuration state ​
The header states where the current values came from, which is what tells you whether the panel or something else is in charge:
| Field | What it means |
|---|---|
| Stored profile | The profile this panel has on record. Custom means the values match neither a preset nor a saved profile. |
| Running profile | What the server is actually running. |
| Last applied | When this panel last applied a profile. Never applied from this panel means the values on the server were not set here. |
| Server | The PostgreSQL release. |
| Restart | Whether a change is waiting for a restart. |
Profiles ​
A profile is a starting point rather than a fixed setting:
- Balanced - a general-purpose starting point.
- Web transactions - for many small, short queries, which is what most hosted sites produce.
- Reporting - for fewer, heavier queries.
- Custom - what the page shows when the values match no preset.
A built-in preset is computed for this particular machine rather than being a fixed table of numbers, so the same preset lands on different values on a different server.
Reset to server defaults puts every parameter back to what PostgreSQL itself would use.
Parameters ​
Every field, its unit, and its accepted range come from the running server, so the form cannot offer a value the server would reject. Values are in the unit named in the field label.
Each parameter states what is in effect, what it falls back to, and its source: a value from the configuration file was set explicitly, a value from the default was never set.
A parameter you do not change keeps its value. Leaving a field alone does not reset it.
Parameters marked Restart required are read by PostgreSQL only at startup. Changing one is stored, but does not take effect until the server restarts, and the header says a restart is pending until it does. Plan those changes for a quiet moment: a restart interrupts every open connection, including the sites using them.
Related pages ​
- PostgreSQL - the engine, its state, and the PHP drivers.
- Remote PostgreSQL - access from other hosts.
- Database Settings - the MariaDB equivalent.
- Health - where a stopped database service shows up.