Re: How to avoid SET application_name = ''

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: How to avoid SET application_name = ''
Дата
Msg-id CAMsr+YGiRKTqW1XOcYgopGQJyAbtYXjHYrkqrh4MZ-0aR+N4vg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: How to avoid SET application_name = ''  (Fabio Caiut <caiut@hotmail.com>)
Ответы Re: How to avoid SET application_name = ''  (Sehrope Sarkuni <sehrope@jackdb.com>)
Список pgsql-jdbc


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.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Nuno Zimas
Дата:
Сообщение: Re: user can't access own database after creation
Следующее
От: Edson Richter
Дата:
Сообщение: Re: user can't access own database after creation