Content #
postgresql.conf #
Every configuration parameter is associated with a context, and depending on the context, you can apply changes with or without a cluster restart. Available contexts are as follows:
- internal:
A group of parameters that are set at compile time and therefore cannot be changed at runtime.
- postmaster:
All the parameters that require the cluster to be restarted (that is, to kill the postmaster process and start it again) to activate them.
- sighup:
All the configuration parameters that can be applied with a SIGHUP signal sent to the postmaster process, which is equivalent to issuing a reload signal in the operating system service manager.
- backend and superuser-backend:
All the parameters that can be set at runtime but will be applied to the next normal or administrative connection.
- user and superuser:
A group of settings that can be changed at runtime and are immediately active for normal and administrative connection.
postgresql.auto.conf #
This file is automatically overwritten by PostgreSQL when the configuration is changed at runtime directly within the system, by means of specific administrative statements such as ALTER SYSTEM.
The postgresql.auto.conf file is always loaded at the very last moment, therefore overwriting other settings. In a fresh installation, this file is empty, meaning it will not overwrite any other custom setting.