Skip site navigation (1) Skip section navigation (2)

Re: Establishing remote connections is slow

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <mindas(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Establishing remote connections is slow
Date: 2012-01-17 17:36:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Mindaugas *ak*auskas<mindas(at)gmail(dot)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.)
Actually, where I've seen this sort of problem, it was the client
code which was doing the unnecessary reverse DNS lookup.  What
controls this in psql?

In response to


pgsql-admin by date

Next:From: Kevin GrittnerDate: 2012-01-17 17:41:13
Subject: Re: [ADMIN] Post Removal
Previous:From: Tom LaneDate: 2012-01-17 17:18:37
Subject: Re: Establishing remote connections is slow

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group