Re: Severe performance degradation when using the 9.2-1000 JDBC 4 driver - Mailing list pgsql-jdbc

From Tsunakawa, Takayuki
Subject Re: Severe performance degradation when using the 9.2-1000 JDBC 4 driver
Date
Msg-id 0A3221C70F24FB45833433255569204D08B08188@G01JPEXMBYT03
Whole thread Raw
In response to Re: Severe performance degradation when using the 9.2-1000 JDBC 4 driver  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
> From: pgsql-jdbc-owner@postgresql.org
> On Thu, Oct 18, 2012 at 8:18 AM, Craig Ringer <ringerc@ringerc.id.au> wrote:
> > On 10/18/2012 05:17 PM, Mikko Tiihonen wrote:
> >>
> >> I think the DNS lookup is part of the JDBC failover connection patch
> >> that I created.
> >> I initially used a InetSocketAddress.getHostString() that does not do
> >> any DNS lookups, but since that method was added in Java7 I had to
> >> revert to
> >> getHostName() method which does.
> >>
> >> I see following options:
> >
> >
> > 0) Revert the JDBC failover patch or require a connection parameter to
> > enable it
> >
> >
> >> 1) modify the code so that is uses reflection and if Java7 is
> >> detected it will use the no-lookup method
> >
> >
> > Gah! no! Not only will this not work in most SecurityManager contexts,
> > but it's slow and horrid.
> 
> Surely there must be a way to detect that you are on Java7 without reflection ?

System.getProperty("java.version") will do.

http://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html

+1 to choice 1.


Regards

pgsql-jdbc by date:

Previous
From: Sérgio Saquetim
Date:
Subject: Re: Severe performance degradation when using the 9.2-1000 JDBC 4 driver
Next
From: Kris Jurka
Date:
Subject: Re: Severe performance degradation when using the 9.2-1000 JDBC 4 driver