From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Mindaugas Žakšauskas <mindas@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Establishing remote connections is slow
Date: Tue, 17 Jan 2012 12:18:37 -0500
Message-ID: <20244.1326820717@sss.pgh.pa.us> (raw)
In-Reply-To: <4F15517F0200002500044874@gw.wicourts.gov>
References: <CAKTEH83nqC5NBZjWJ2ZAW8eBMWjW3N6G3RhbsWy68rMgf=MF1Q@mail.gmail.com>
<4F15517F0200002500044874@gw.wicourts.gov>
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> 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.
Having log_hostname off is supposed to prevent us from attempting a
reverse DNS lookup ... but it would be worth checking into whether one
is happening anyway. (I would think though that such activity would
be visible in strace/truss output. Perhaps you should turn log_hostname
*on* and verify that you see the lookup activity in strace that wasn't
there before.)
regards, tom lane
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: tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, mindas@gmail.com
Subject: Re: Establishing remote connections is slow
In-Reply-To: <20244.1326820717@sss.pgh.pa.us>
* 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