Re: BUG #1045: hostname lookup in psql or libpg.sl does work - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1045: hostname lookup in psql or libpg.sl does work
Date
Msg-id 19589.1073614953@sss.pgh.pa.us
Whole thread Raw
In response to BUG #1045: hostname lookup in psql or libpg.sl does work  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List pgsql-bugs
"PostgreSQL Bugs List" <pgsql-bugs@postgresql.org> writes:
> psql (and libpg.sl via the DBI and DBD::Pg interface) report:
> psql: could not translate host name "ysolde" to address: host nor service
> provided, or not known

Couldn't duplicate this using HP's testdrive systems (HP 11.11).

I do get a message of exactly that spelling when providing a
deliberately incorrect hostname, though.  I suspect pilot error on
your part, or misconfiguration of your DNS setup.

$ uname -a
HP-UX spe191 B.11.11 U 9000/800 1865940626 unlimited-user license

-- spe176 is a nearby machine that's not in /etc/hosts:

$ nslookup spe176
Using /etc/hosts on:  spe191

looking up FILES
Trying DNS
Name:    spe176.testdrive.hp.com
Address:  192.233.54.176

$ psql -l -p 5440 -h spe176
psql: could not connect to server: Connection refused
        Is the server running on host "spe176" and accepting
        TCP/IP connections on port 5440?
$ psql -l -p 5440 -h spe176.testdrive.hp.com
psql: could not connect to server: Connection refused
        Is the server running on host "spe176.testdrive.hp.com" and accepting
        TCP/IP connections on port 5440?
$ psql -l -p 5440 -h spe17dddfqz
psql: could not translate host name "spe17dddfqz" to address: host nor service provided, or not known
$

            regards, tom lane

pgsql-bugs by date:

Previous
From: Jason Tishler
Date:
Subject: Re: Cygwin PostgreSQL 7.4.1 rules regression test failure
Next
From: Jonathan Purvis
Date:
Subject: JDBC driver doesn't handle NaN values