Logging configuration changes - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Logging configuration changes
Date
Msg-id 200907122255.31856.peter_e@gmx.net
Whole thread Raw
Responses Re: Logging configuration changes
Re: Logging configuration changes
List 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?


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: concurrent index builds unneeded lock?
Next
From: Pavel Stehule
Date:
Subject: fix: plpgsql: return query and dropped columns problem