Re: [PATCH] HINT: pg_hba.conf changed since last config reload

From: Steve Singer <steve(at)ssinger(dot)info>
To: Alex Shulgin <ash(at)commandprompt(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date: 2014-12-20 17:11:30
Message-ID: BLU436-SMTP1022A8B9C570614720C737ADC680@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-12-20 17:12:04 Re: Initdb-cs_CZ.WIN-1250 buildfarm failures
Previous Message Noah Misch 2014-12-20 16:48:43 Re: Initdb-cs_CZ.WIN-1250 buildfarm failures