| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabio Caiut <caiut(at)hotmail(dot)com> |
| Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: How to avoid SET application_name = '' |
| Date: | 2015-12-03 15:44:30 |
| Message-ID: | CAMsr+YGiRKTqW1XOcYgopGQJyAbtYXjHYrkqrh4MZ-0aR+N4vg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 27 November 2015 at 00:35, Fabio Caiut <caiut(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edson Richter | 2015-12-03 16:00:40 | Re: user can't access own database after creation |
| Previous Message | Nuno Zimas | 2015-12-03 15:39:33 | Re: user can't access own database after creation |