From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Steve Singer <ssinger_pg(at)sympatico(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: log_hostname and pg_stat_activity |
Date: | 2011-01-30 22:12:35 |
Message-ID: | AANLkTinPk1cExnFcX88CpoxigfChSc+rsP86aG+WytJ5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 30, 2011 at 4:30 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On sön, 2011-01-30 at 15:03 -0500, Robert Haas wrote:
>> On Tue, Jan 18, 2011 at 7:24 PM, Steve Singer
>> <ssinger_pg(at)sympatico(dot)ca> wrote:
>> > If my connection is authorized through a line in pg_hba that uses
>> > client_hostname then the column shows what I expect even with
>> log_hostname
>> > set to off.
>> >
>> > However if I connect with a line in pg_hba that matches on an IP
>> network
>> > then my client_hostname is always null unless log_hostname is set to
>> true.
>> > This is consistent with the behavior you describe but I think the
>> average
>> > user will find it a bit confusing.
>>
>> I agree. I'm not sure there's enough value to this feature to warrant
>> the amount of user confusion this is likely to produce.
>
> What alternative behavior would you suggest?
I don't know. As I said in my previous email, I'd either (a) forget
the whole thing or (b) make sure that the documentation is *extremely*
explicit about what the behavior is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-01-30 22:14:50 | Re: WIP: RangeTypes |
Previous Message | Robert Haas | 2011-01-30 22:08:12 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |