From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Application name patch - v3 |
Date: | 2009-11-25 13:28:14 |
Message-ID: | 937d27e10911250528p1edf0a4ch5e0b09a34fdafa71@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 25, 2009 at 1:22 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On Thursday 22 October 2009 15:07:13 Dave Page wrote:
>> Updated patch attached. Per discussion, this:
>>
>> - Changes the envvar name to PGAPPNAME
>> - Removes support for setting application_name in the startup packet,
>> and instead sends an explicit SET command as part of the connection
>> setup in PQconnectPoll. In order to avoid adding to the
>> application-visible connection states, this is overloaded on the
>> CONNECTION_SETENV state which is only used in the v2 protocol at
>> present and seems like an ideal fit for such a similar use.
>>
>> Other features are as per the last version.
> One more question: Per my reading of the discussion (which very well might be
> flawed), wasnt the plan to limit the availale characters in the application
> name to ascii?
That was suggested, but I thought the eventual outcome was to not bother.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2009-11-25 13:33:18 | Re: Application name patch - v3 |
Previous Message | Andres Freund | 2009-11-25 13:22:43 | Re: Application name patch - v3 |