When I connect to a non-existing server over Unix-domain sockets I now
simply get

createdb: could not connect to database template1: could not create socket: No such file or directory

There used to be a more verbose message along the lines of "Is the server
running on ... and accepting connections on ...?" which is still in the
source but apparently does not get called because of the IPv6 changes.

-- 
Peter Eisentraut   peter_e@gmx.net


Tue, 18 Mar 2003 23:06:21 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
libpq's error messages not working as before
Peter Eisentraut <peter_e@gmx.net> writes:
> When I connect to a non-existing server over Unix-domain sockets I now
> simply get

> createdb: could not connect to database template1: could not create socket: No such file or directory

I'm not getting quite that behavior --- how did you invoke it exactly?

But I agree that the error message is broken in the IPv6 code.  On a
machine with no IPv6 support (HPUX 10.20), I still get the right thing
from CVS tip:

$ createdb -p 7777
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.7777"?
createdb: database creation failed
$

But with the IPv6 code compiled (Red Hat 8.0), the error message is the
wrong one (it's for TCP not Unix connections):

$ createdb -p 7777
psql: could not connect to server: No such file or directory
        Is the server running on host ??? and accepting
        TCP/IP connections on port 7777?
createdb: database creation failed
$

I noticed this some weeks ago, but had not got round to investigating yet.

			regards, tom lane

Tue, 18 Mar 2003 18:45:20 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq's error messages not working as before 