Configuration — Current GUC Values + Diff
Browse every GUC in your cluster, see what differs from default, what would benefit from tuning.
The Configuration page is every value from pg_settings in one searchable, filterable table. The whole catalog, with the metadata that matters: current value, boot value (what it was at server start, before any ALTER SYSTEM took effect), default, min, max, source, and whether a restart is needed to change it.
Columns
Setting name + category (Resource Usage / WAL / Query Tuning / etc.). Current value. Boot value — what it was at server start. Default, min, max. Source — default / configuration file / command line / database / user / session / environment variable / override. Restart — postmaster context, marked with a yellow badge. MonPG recommendation — green check if it matches our baseline, amber tip if we'd suggest a change.
Useful filters
"Differs from default" shows everything that's been customized on this cluster. "Drift from MonPG baseline" is the same as the Settings → Tuning diff but inline here. "Source = database/user" surfaces per-DB or per-role overrides — set via ALTER DATABASE … SET or ALTER ROLE … SET — which are easy to forget about and hard to find without this filter.
Apply a recommendation
Click any setting to see the SQL or config snippet for your provider's surface (Parameter Group on RDS, Server Parameter on Azure, Cloud SQL Flag, plain postgresql.conf on self-hosted). MonPG never auto-applies changes — you copy-paste into your own change-management process. We deliberately chose this; auto-applying GUC changes from a monitoring tool is the kind of feature that goes wrong in spectacular ways.