Home > Uncategorized > postgresql configuration settings changes and where they are reflected

postgresql configuration settings changes and where they are reflected

pg_ctl reload documentation reflects that it will reload “some configuration-file options that do not require a complete restart to take effect.”

After making a change, triggering a reload, you can take a look in the following table view to review the active settings: pg_settings. Note the context column value for the setting to figure out which scope it affects: user, sighup, or postmaster. This will also tell you what needs to happen in order for the setting to affect the postgresql instance (log off and back on, send a sighp (via pg_ctl), or kill and respawn postmaster).

Quick note: `pg_ctl reload` is actually triggered with `service postgresql reload`, so you don’t need to worry about the overhead or mistake prone syntax.

P.S.:
The `ssl` directive within postgresql.conf only gets reflected on restart not on reload.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: