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

From: Alex Shulgin <ash(at)commandprompt(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Steve Singer <steve(at)ssinger(dot)info>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] HINT: pg_hba.conf changed since last config reload
Date: 2014-12-19 16:49:41
Message-ID: 87vbl7vb2y.fsf@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Craig Ringer <craig(at)2ndquadrant(dot)com> writes:

> On 12/19/2014 11:41 PM, 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
>
> Well, actually, the whole point was that the user who's connecting
> (likely also the "DBA") will see a HINT telling them that there's more
> in the logs.
>
> But that got removed.

While it sounds useful at first glance, I believe Peter's arguments
upthread provide enough justification to avoid sending the hint to the
client.

--
Alex

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arthur Silva 2014-12-19 17:04:40 Re: Commitfest problems
Previous Message Robert Haas 2014-12-19 16:38:23 Re: NUMERIC private methods?