Re: Application name patch - v2

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Harald Armin Massa <chef(at)ghum(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Application name patch - v2
Date: 2009-10-21 15:29:29
Message-ID: 603c8f070910210829h481ebd6g18e693af43a75061@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 21, 2009 at 11:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Tom Lane wrote:
>>> FWIW, I would prefer PGAPPNAME to PGAPPLICATIONNAME which is what
>
>> We don't usually use abbreviations, so how about PGCLIENTNAME  or some such?
>
> Not sure I believe that argument.  Among the set of existing libpq
> environment variables I see
>
> PGHOSTADDR
> PGSSLCERT
> PGSSLCRL
> PGKRBSRVNAME
> PGTZ
> PGSYSCONFDIR
>
> so it can hardly be said that there's a policy of avoiding
> abbreviations.  PGCLIENTNAME would be better than PGAPPLICATIONNAME
> I guess, but I still prefer the other.

I also like PGAPPNAME better, for the same reasons as Tom.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-10-21 15:29:35 Re: Application name patch - v2
Previous Message Tom Lane 2009-10-21 15:25:48 Re: Application name patch - v2