Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 7238D1DA4C1F for ; Tue, 17 Jan 2012 12:46:50 -0400 (AST) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RnCBL-0003C4-QM for pgsql-admin@postgresql.org; Tue, 17 Jan 2012 16:46:49 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Tue, 17 Jan 2012 10:46:33 -0600 Message-Id: <4F15517F0200002500044874@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Tue, 17 Jan 2012 10:46:23 -0600 From: "Kevin Grittner" To: "=?ISO-8859-15?Q?Mindaugas=20=B4ak=A8auskas?=" , Subject: Re: Establishing remote connections is slow References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201201/66 X-Sequence-Number: 38978 Mindaugas =B4ak=A8auskas wrote: =20 > The essence is that establishing remote connection takes anywhere > from 10 to 30 seconds. Once connected, the queries are fast =20 The only time I=27ve seen something similar, there was no reverse DNS entry to go from IP address to host name. Adding that corrected the issue. I would try that. =20 If that fixes it, the questions would be whether PostgreSQL is doing an unnecessary reverse DNS lookup. =20 -Kevin