Re: BUG #8225: logging options don't change after reload

Tom Lane wrote:
> jeff@pgexperts.com writes:
> > What happens is that we change various logging options in postgresql.conf,
> > then reload, and every so often, the settings don't seem to take effect even
> > though they are logged as being changed.
>
> FWIW, the "parameter changed" messages are logged when the postmaster
> process updates its values of the GUCs.  The particular options you're
> complaining of here, though, are not actually checked in the postmaster
> --- they're used in the checkpointer or syslogger processes
> respectively.  So one theory about this would be that those processes
> aren't absorbing the GUC updates, perhaps because the SIGHUP signals the
> postmaster should be sending them are getting lost.

Another idea is that postmaster sees the changed file but the other
processes see an older version of it -- which would be pretty bizarre,
but ..

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services