From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Mindaugas Žakšauskas <mindas@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Establishing remote connections is slow
Date: Tue, 17 Jan 2012 10:46:23 -0600
Message-ID: <4F15517F0200002500044874@gw.wicourts.gov> (raw)
In-Reply-To: <CAKTEH83nqC5NBZjWJ2ZAW8eBMWjW3N6G3RhbsWy68rMgf=MF1Q@mail.gmail.com>
References: <CAKTEH83nqC5NBZjWJ2ZAW8eBMWjW3N6G3RhbsWy68rMgf=MF1Q@mail.gmail.com>
Mindaugas Žakšauskas<mindas@gmail.com> wrote:
> The essence is that establishing remote connection takes anywhere
> from 10 to 30 seconds. Once connected, the queries are fast
The only time I've 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.
If that fixes it, the questions would be whether PostgreSQL is doing
an unnecessary reverse DNS lookup.
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, mindas@gmail.com
Subject: Re: Establishing remote connections is slow
In-Reply-To: <4F15517F0200002500044874@gw.wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox