Postgres Pro
Downloads
Home   >   mailing lists

How to detect if Postgres needs a restart when configuration changes - Mailing list pgsql-admin

From Strahinja Kustudić
Subject How to detect if Postgres needs a restart when configuration changes
Date
Msg-id CADKbJJVwK9Gx=UEAZQthz-_6kOOcd36_qnyX0+R9StD4bmcH6w@mail.gmail.com
Whole thread Raw
Responses Re: How to detect if Postgres needs a restart when configuration changes  (Payal Singh <payal@omniti.com>)
Re: How to detect if Postgres needs a restart when configuration changes  (Ian Barwick <ian@2ndquadrant.com>)
Re: How to detect if Postgres needs a restart when configuration changes  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-admin
Tree view
I am automating Postgres deployment on Linux and I need to check if Postgres needs to be restarted when a configuration parameter that requires a restart changes, e.g. when you change wal_level. Is there a way to detect a parameter which requires a restart was changed?

Reading the log file after sending SIGHUP is not possible to automate. I know I can query pg_settings and then compare relevant parameters from the conf file, but that means I will need to check all parameters which I set and which require a restart. I only need to know if postgres requires a restart.

Strahinja Kustudić | Lead System Engineer | Nordeus

pgsql-admin by date:

Previous
From: DrakoRod
Date:
Subject: Re: The tables partitioning affects the indexes?
Next
From: Payal Singh
Date:
Subject: Re: How to detect if Postgres needs a restart when configuration changes