Re: [PATCH] HINT: pg_hba.conf changed since last config reload - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date
Msg-id 20141127134904.GC16294@momjian.us
Whole thread Raw
In response to Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Nov  6, 2014 at 05:46:42PM -0500, Peter Eisentraut wrote:
> Finally, the fact that a configuration change is in progress is
> privileged information.  Unprivileged users can deduct from the presence
> of this message that administrators are doing something, and possibly
> that they have done something wrong.
> 
> I think it's fine to log a message in the server log if the pg_hba.conf
> file needs reloading.  But the client shouldn't know about this at all.

Should we do this for postgresql.conf too?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Add CREATE support to event triggers
Next
From: Michael Paquier
Date:
Subject: Re: Fillfactor for GIN indexes