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

From Steve Singer
Subject Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date
Msg-id BLU436-SMTP1022A8B9C570614720C737ADC680@phx.gbl
Whole thread Raw
In response to Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Alex Shulgin <ash@commandprompt.com>)
Responses Re: [PATCH] HINT: pg_hba.conf changed since last config reload  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 12/19/2014 10:41 AM, Alex Shulgin wrote:
> I don't think so.  The scenario this patch relies on assumes that the
> DBA will remember to look in the log if something goes wrong, and in
> your case there would be a message like the following:
>
> WARNING:  pg_hba.conf not reloaded
>
> So an extra hint about file timestamp is unneeded.

That makes sense to me.
I haven't found any new issues with this patch.
I think it is ready for a committer.


>
> --
> Alex
>
>




pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Initdb-cs_CZ.WIN-1250 buildfarm failures
Next
From: Tom Lane
Date:
Subject: Re: Initdb-cs_CZ.WIN-1250 buildfarm failures