Re: Messed up dblink...

From: Jerry LeVan <Jerry(dot)Levan(at)EKU(dot)EDU>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Messed up dblink...
Date: 2009-03-21 17:17:07
Message-ID: FF452D69-B8BF-4288-B3E9-E30CBE8AC18C@EKU.EDU
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Mar 21, 2009, at 12:37 PM, Tom Lane wrote:

> Jerry LeVan <jerry(dot)levan(at)eku(dot)edu> writes:
>> Something seems to have messed up my dblink interface...
>> The only thing I can think that has changed the last week
>> was the installation of 8.3.7.
>
> What version were you using beforehand? Are you *sure* nothing else
> in
> your environment has changed?
>
>> levan=# select dblink_connect('host=mbp user=levan dbname=levan
>> password=foobar')
>> levan-# ;
>> ERROR: could not establish connection
>> DETAIL: could not translate host name "mbp" to address: Temporary
>> failure in name resolution
>
> ... because it is really, really hard to see how that particular
> failure could arise from anything except a broken DNS configuration.
>
> Try "nslookup mbp" at the shell command prompt. If that fails with
> a similar error message, Postgres is not at fault.
>
> regards, tom lane

Ok,

I found that for all of my boxen that if I connected to 'server' that
I could not connect back via dblink to the original host!

The nslookup worked fine in every case...

'server' is also my local nameserver. I took a flier and rebooted
the rascal and everything started working again :)

Thanks for the hint.

Jerry

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nick 2009-03-21 22:48:01 How to avoid multiple table scan with "NOT IN"
Previous Message Tom Lane 2009-03-21 16:37:48 Re: Messed up dblink...