On Thu, Nov 27, 2014 at 8:49 AM, Bruce Momjian <br...@momjian.us> wrote: > 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?
It doesn't really make sense; or at least, the exact same thing doesn't make any sense. If an authentication attempt fails unexpectedly, it might be because of a pg_hba.conf change that wasn't reloaded, so it makes sense to try to tip off the DBA. But it can't really be because of a pending postgresql.conf change that hasn't been reloaded, because those don't generally affect authentication. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers