Re: Establishing remote connections is slow
| От | Tom Lane |
|---|---|
| Тема | Re: Establishing remote connections is slow |
| Дата | |
| Msg-id | 20244.1326820717@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Establishing remote connections is slow ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: Establishing remote connections is slow
|
| Список | pgsql-admin |
"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
В списке pgsql-admin по дате отправления: