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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: 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-11-08 02:49:41
Message-ID: CA+Tgmob5UQD8k2Ned1HYDfdo8Kks82EJWBpfkt7AQXwm58T3Gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 6, 2014 at 5:46 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> I think it's fine to log a message in the server log if the pg_hba.conf
> file needs reloading. But the client shouldn't know about this at all.

I agree.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-11-08 03:27:14 Re: BRIN indexes - TRAP: BadArgument
Previous Message Robert Haas 2014-11-08 02:47:30 Re: BUG #11867: Strange behaviour with composite types after resetting database tablespace