| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Fabio Caiut <caiut(at)hotmail(dot)com> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: How to avoid SET application_name = '' |
| Date: | 2015-11-25 16:54:56 |
| Message-ID: | CAB=Je-Hx6C2aLmfDDkY07PGDdAHML0a9Aa+=VCHzkxxmUEBLdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2015-11-25 16:56:26 | Re: How to avoid SET application_name = '' |
| Previous Message | Fabio Caiut | 2015-11-25 15:20:57 | How to avoid SET application_name = '' |