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
inJava7 I had to revert to getHostName() method which does.
I see following options:
1) modify the code so that is uses reflection and if Java7 is detected it will use the no-lookup method
2) wait 4 months until Oracle drops Java6 support (Java6 was supposed to be EOL already few months back) and use the
no-lookupvariant
3) let the code stay as is and let users fix their dns servers
-Mikko
________________________________________
From: pgsql-jdbc-owner@postgresql.org [pgsql-jdbc-owner@postgresql.org] on behalf of Craig Ringer
[ringerc@ringerc.id.au]
Sent: 18 October 2012 12:03
To: Sérgio Saquetim
Cc: pgsql-jdbc@postgresql.org; Rafael dos Santos Silva
Subject: Re: [JDBC] Severe performance degradation when using the 9.2-1000 JDBC 4 driver
On 10/18/2012 12:16 PM, Sérgio Saquetim wrote:
> I can confirm the problem, it's taking about 4000ms to get a Connection.
That sounds like a broken DNS or reverse DNS setup in your environment,
it's about right for your average DNS timeout.
--
Craig Ringer
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc