Logging configuration changes

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Logging configuration changes
Date: 2009-07-12 19:55:31
Message-ID: 200907122255.31856.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On occasion, I would have found it useful if a SIGHUP didn't only log *that*
it reloaded the configuration files, but also logged *what* had changed
(postgresql.conf changes in particular, not so much interested in
pg_hba.conf). Especially in light of the common mistake of forgetting to
uncomment a changed value, this would appear to be useful.

Comments?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-07-12 20:25:44 fix: plpgsql: return query and dropped columns problem
Previous Message Greg Stark 2009-07-12 15:52:03 Re: concurrent index builds unneeded lock?