Sorry - I didn't get a chance to actually look at this patch until now.
The application_name should be set as a connection string parameter,
not an explicit SET command. This ensures that the application name is
included in the initial connection log message, and avoids a round
trip with the SET query. PQconninfoParse can be used to test if libpq
supports application_name at runtime.
I suspect the patch is also missing some changes to the debugger.
On Tue, Dec 29, 2009 at 5:39 PM, <svn@pgadmin.org> wrote:
> Author: guillaume
>
> Date: 2009-12-29 17:39:36 +0000 (Tue, 29 Dec 2009)
>
> New Revision: 8145
>
> Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=8145&view=rev
>
> Log:
> Use application_name for each window.
> Add support of the new application_name column in activity report (8.5).
> (fixes ticket #116)
>
>
> Modified:
> trunk/pgadmin3/CHANGELOG
> trunk/pgadmin3/pgadmin/db/pgConn.cpp
> trunk/pgadmin3/pgadmin/frm/frmConfig.cpp
> trunk/pgadmin3/pgadmin/frm/frmEditGrid.cpp
> trunk/pgadmin3/pgadmin/frm/frmHbaConfig.cpp
> trunk/pgadmin3/pgadmin/frm/frmMainConfig.cpp
> trunk/pgadmin3/pgadmin/frm/frmQuery.cpp
> trunk/pgadmin3/pgadmin/frm/frmStatus.cpp
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com