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 AANLkTimS3qKxL=f1AMBa=tRWW+5oqeOvsSTcZvnK+388@mail.gmail.com
Whole thread Raw
In response to Re: log_hostname and pg_stat_activity  (Steve Singer <ssinger_pg@sympatico.ca>)
Responses Re: log_hostname and pg_stat_activity  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
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.

But if we're going to do it anyway we at least need to do this:

> I would be inclined to add an entry for these views in catalogs.sgml that
> where we can then give users a pointer that they need to set log_hostname to
> get anything out of this column.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Error code for "terminating connection due to conflict with recovery"
Next
From: Robert Haas
Date:
Subject: Re: Visual Studio 2010/Windows SDK 7.1 support