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

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 14:24:59
Message-ID: CABs1bs1_oVf4VDX9ysE0_uHkrkwt101YTkPyvUgTJtTTMRj=vQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ah, gotcha! I guess whatever sample I was originally copying from used
hostaddr for some reason.. Thanks for the clarification, Tom!

On Wed, May 15, 2013 at 6:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2013-05-15 14:48:18 Re: Re: volatile void returning function not executed as often as expected in sql function
Previous Message Tom Lane 2013-05-15 14:12:39 Re: FATAL: database "a/system_data" does not exist