On 12/20/14 12:11 PM, Steve Singer wrote: > 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.
There were later comments in this thread that disagreed with the extra logging infrastructure, and there were some questions about whether it should only log on failed authentication attempts. Altogether, still some open questions about behavior and implementation approach. So I'm marking this as returned with feedback for now. Personally, I think this could be a useful feature, but it needs more fine-tuning. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
