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

From Andres Freund
Subject Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date
Msg-id 20150116170716.GJ16991@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 2015-01-16 18:01:24 +0100, Andres Freund wrote:
> 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 a 'WARNING: client authentication failed/succeeded with a
outdated pg_hba.conf in effect' would actually be a good way to present
this. It's not only failed logins where this is relevant.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: proposal: row_to_array function
Next
From: Heikki Linnakangas
Date:
Subject: Re: pg_rewind in contrib