PostgreSQL Settings shows server configuration values collected from a monitored PostgreSQL instance. Use it to review configuration when investigating performance or reliability.
What To Review
- Memory-related settings.
- Logging settings.
- Autovacuum and maintenance settings.
- Connection settings.
- Query planner or workload-related settings where available.
Workflow
- Open Settings under the PostgreSQL server.
- Search or sort configuration values.
- Compare settings with Memory, I/O, and Health Checks.
- Change PostgreSQL configuration only through your normal database change process.
How To Use PostgreSQL Configuration Evidence
PostgreSQL Settings helps explain why a server behaves the way it does. Configuration values affect memory use, logging, autovacuum, planner behavior, connection limits, checkpoint behavior, and maintenance work. Use this page when health checks identify a configuration concern or when performance evidence suggests a setting may be involved.
Do not tune settings in isolation. Compare memory settings with PostgreSQL Memory, storage behavior with PostgreSQL I/O, slow query symptoms with PostgreSQL Queries, and warnings with PostgreSQL Health Checks. Some settings are safe to review frequently but risky to change without testing.
Configuration also varies between self-managed PostgreSQL and managed cloud services. Cloud providers may restrict certain settings or expose them through parameter groups rather than direct configuration files.
PostgreSQL Settings FAQ
Should I copy settings from another PostgreSQL server?
No. Settings should match workload, server size, PostgreSQL version, and hosting model.
Why is a setting not editable?
Managed services, permissions, restart requirements, or provider parameter groups may control how settings are changed.
Where do I find logging-related evidence?
Use PostgreSQL Server Log and compare logging settings on this page.
Next Steps After Reviewing Settings
After identifying a setting of interest, confirm whether it can be changed online, requires a reload, or requires a restart in your PostgreSQL environment. Managed cloud services may require parameter group changes instead of direct configuration edits. Record the current value and reason for change before adjusting production settings.