From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mindaugas Žakšauskas <mindas(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Establishing remote connections is slow |
Date: | 2012-01-17 15:41:12 |
Message-ID: | 16644.1326814872@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
=?UTF-8?Q?Mindaugas_=C5=BDak=C5=A1auskas?= <mindas(at)gmail(dot)com> writes:
>> What about "psql -h localhost", ie physically local connection but
>> via TCP not unix socket?
> user(at)dbserver> psql -h 127.0.0.1 -p5432 -U user -W db
> This works fast. But
> user(at)dbserver> psql -h <IP> -p5432 -U user -W db
> (where <IP> is the multipath interface)
> This is slow! So it is definitely something network-related or
> something how PostgreSQL deals with multipath interface.
Hm. AFAIR postgres doesn't know anything particular about multipath
interfaces --- it just listens where you tell it to. So I'm thinking
this is a system-level issue. It still seems like it could be DNS
lookup related though. Do you have log_hostname turned on, and if so
does turning it off make a difference?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Domiciano | 2012-01-17 15:41:34 | Post Removal |
Previous Message | Mindaugas Žakšauskas | 2012-01-17 15:31:23 | Re: Establishing remote connections is slow |