Re: dblink does not resolve DNS, but works with IP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Christensen <mike(at)kitchenpc(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: dblink does not resolve DNS, but works with IP
Date: 2013-05-15 13:08:37
Message-ID: 24298.1368623317@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Mike Christensen <mike(at)kitchenpc(dot)com> writes:
> Though I'm a bit curious why there's a host and hostaddr. Why can't it
> just resolve whatever you give it?

Well, it will ... if you use the "host" parameter. The whole point of
"hostaddr" is that for that parameter, it will not try a DNS lookup.
You'd only use that if you had issues with the speed or reliability
of your DNS service.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2013-05-15 13:55:42 Re: FATAL: database "a/system_data" does not exist
Previous Message sumita 2013-05-15 12:45:33 Re: FATAL: database "a/system_data" does not exist