Re: How to avoid SET application_name = ''

Поиск
Список
Период
Сортировка
От Sehrope Sarkuni
Тема Re: How to avoid SET application_name = ''
Дата
Msg-id CAH7T-aoGF8MGNim2SUg6tDM7HMeKZgMnVeh5WzhJJOx0C4mEAQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: How to avoid SET application_name = ''  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-jdbc
Дерево обсуждения
On Thu, Dec 3, 2015 at 10:44 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
On 27 November 2015 at 00:35, Fabio Caiut <caiut@hotmail.com> wrote:
Hi, 
Vladimir, Thomas ... you're right.

The glassfish guys analyzed dumps and look in the glassfish sources, the problem is there. 
They told me pool calls setClientInfo for each query!! 


If an application_name is passed on the JDBC URL, PgJDBC should really send it in the startup packet, not a follow-up SET anyway. I haven't checked to see if it currently does.

Yes if the connection property "assumeMinServerVersion" is set to at least 9.0 then the application_name will be set in the start up packet (rather than as a separate query after the connection is established). There's no default value though as older server versions will not support it.

Regards,
-- Sehrope Sarkuni

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: "Markus KARG"
Дата:
Сообщение: Re: Migration to Maven
Следующее
От: Georg Brünsing
Дата:
Сообщение: jdbc high memory consumption for RAISE NOTICE output using function-call in Java