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

From Tom Lane
Subject Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date
Msg-id 29492.1421428873@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: [PATCH] HINT: pg_hba.conf changed since last config reload
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> Why don't we just add emit a NOTICE or WARNING in the relevant place
> saying that pg_hba.conf is outdated? Then the server won't log those if
> configured appropriately, which doesn't seem like a bad thing. Note that
> <= ERROR messages aren't sent to the client during authentication.

I think people felt that sending that information to the client wouldn't
be a good idea security-wise.  But I'd phrase it as "why not just emit
a LOG message?".  I agree that new logging infrastructure seems like
overkill.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: speedup tidbitmap patch: cache page
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: row_to_array function