Re: log_hostname and pg_stat_activity

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Steve Singer <ssinger_pg(at)sympatico(dot)ca>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: log_hostname and pg_stat_activity
Date: 2011-01-30 20:03:35
Message-ID: AANLkTimS3qKxL=f1AMBa=tRWW+5oqeOvsSTcZvnK+388@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-30 20:06:01 Re: Visual Studio 2010/Windows SDK 7.1 support
Previous Message Robert Haas 2011-01-30 19:56:17 Re: Error code for "terminating connection due to conflict with recovery"