From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: option --application_name for psql |
Date: | 2013-05-14 19:33:54 |
Message-ID: | CABUevEwiCjOKkAmwfGAY5FSx59NV-SVNXQSU0Hws+BxWTS+T6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 14, 2013 at 9:25 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 2013/5/14 Erik Rijkers <er(at)xs4all(dot)nl>:
>> On Tue, May 14, 2013 21:04, Pavel Stehule wrote:
>>> Hello
>>>
>>> we like to use psql in combination with bash - just like postgresql driver.
>>>
>>> Actually there is no simple possibility (from command line) to set
>>> application_name. We would to use different name than psql - for
>>> example "splunk", ...
>>>
>>> I tested PGAPPNAME, but it doesn't work.
>>>
>>
>> It does work:
>>
>> $ PGAPPNAME=splunk psql -c "select application_name from pg_stat_activity;"
>> application_name
>> ------------------
>> splunk
>> (1 row)
>>
>> But perhaps I misunderstood your intention?
>>
>
> I was wrong - PGAPPNAME works, thank you
>
> but command line --application_name option should be a useful option I
> am thinking still
>
That goes for a lot of the parameters that go in a connection string,
I'm not sure application_name is common enough to have it's own
argument if other parameters don't. And you can still set it as long
as you use psql in "connection string mode", as you can with all the
libpq parameters.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-05-14 19:36:48 | Re: proposal: option --application_name for psql |
Previous Message | Pavel Stehule | 2013-05-14 19:25:00 | Re: proposal: option --application_name for psql |