FW: How to avoid SET application_name = ''

From: Fabio Caiut <caiut(at)hotmail(dot)com>
To: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: FW: How to avoid SET application_name = ''
Date: 2015-11-25 19:38:34
Message-ID: SNT152-W238479F42F88643A2262D9A5050@phx.gbl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

+list(sorry)

From: caiut(at)hotmail(dot)com
To: sitnikov(dot)vladimir(at)gmail(dot)com
Subject: RE: [JDBC] How to avoid SET application_name = ''
Date: Wed, 25 Nov 2015 15:03:06 -0200

Hi Vladimir,
I have access just to postgres servers, I'll ask appserver guys to get thread dumps.
Thank you for help!
Caiut

> Date: Wed, 25 Nov 2015 19:54:56 +0300
> Subject: Re: [JDBC] How to avoid SET application_name = ''
> From: sitnikov(dot)vladimir(at)gmail(dot)com
> To: caiut(at)hotmail(dot)com
> CC: pgsql-jdbc(at)postgresql(dot)org
>
> As far as I can tell, there is no option to completely disable "set
> application_name" feature via property.
>
> Is SQL appears when client calls
> Connection#setClientInfo("ApplicationName", ...) or
> Connection#setClientInfo(Properties).
>
> It make sense to avoid setting the same application name again and
> again for the same connection.
> Can you please file an issue at https://github.com/pgjdbc/pgjdbc/issues?
>
> In the mean time, it would be good if you could capture thread dumps
> from the application (e.g. 100 dumps with 10 second intervals under
> typical load) and grep setClientInfo. That would point out the line in
> code that issues that excessive setClientInfo.
>
> Vladimir

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2015-11-25 22:25:17 JDBC 1206 released
Previous Message Thomas Kellerer 2015-11-25 18:25:40 Re: How to avoid SET application_name = ''