Re: How to avoid SET application_name = '' - Mailing list pgsql-jdbc

From Craig Ringer
Subject Re: How to avoid SET application_name = ''
Date
Msg-id CAMsr+YGiRKTqW1XOcYgopGQJyAbtYXjHYrkqrh4MZ-0aR+N4vg@mail.gmail.com
Whole thread Raw
In response to Re: How to avoid SET application_name = ''  (Fabio Caiut <caiut@hotmail.com>)
Responses Re: How to avoid SET application_name = ''  (Sehrope Sarkuni <sehrope@jackdb.com>)
List 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 by date:

Previous
From: Nuno Zimas
Date:
Subject: Re: user can't access own database after creation
Next
From: Edson Richter
Date:
Subject: Re: user can't access own database after creation