Re: log_hostname and pg_stat_activity - Mailing list pgsql-hackers

From Robert Haas
Subject Re: log_hostname and pg_stat_activity
Date
Msg-id AANLkTinPk1cExnFcX88CpoxigfChSc+rsP86aG+WytJ5@mail.gmail.com
Whole thread Raw
In response to Re: log_hostname and pg_stat_activity  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Sun, Jan 30, 2011 at 4:30 PM, Peter Eisentraut <peter_e@gmx.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@sympatico.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


pgsql-hackers by date:

Previous
From: Jan Urbański
Date:
Subject: Re: wildcard search support for pg_trgm
Next
From: Thom Brown
Date:
Subject: Re: WIP: RangeTypes