FW: How to avoid SET application_name = ''
От | Fabio Caiut |
---|---|
Тема | FW: How to avoid SET application_name = '' |
Дата | |
Msg-id | SNT152-W238479F42F88643A2262D9A5050@phx.gbl обсуждение исходный текст |
Ответ на | How to avoid SET application_name = '' (Fabio Caiut <caiut@hotmail.com>) |
Список | pgsql-jdbc |
+list
(sorry)
From: caiut@hotmail.com
To: sitnikov.vladimir@gmail.com
Subject: RE: [JDBC] How to avoid SET application_name = ''
Date: Wed, 25 Nov 2015 15:03:06 -0200
From: caiut@hotmail.com
To: sitnikov.vladimir@gmail.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.vladimir@gmail.com
> To: caiut@hotmail.com
> CC: pgsql-jdbc@postgresql.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
> Subject: Re: [JDBC] How to avoid SET application_name = ''
> From: sitnikov.vladimir@gmail.com
> To: caiut@hotmail.com
> CC: pgsql-jdbc@postgresql.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
В списке pgsql-jdbc по дате отправления: