Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch] - Mailing list pgsql-bugs

From Tom Lane
Subject Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]
Date
Msg-id 4233.978225058@sss.pgh.pa.us
Whole thread Raw
In response to NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]  ("Thomas T. Thai" <tom@minnesota.com>)
Responses Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]  ("Thomas T. Thai" <tom@minnesota.com>)
Re: Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-bugs
"Thomas T. Thai" <tom@minnesota.com> writes:
> psql: connectDBStart() -- connect() failed: No such file or directory
>         Is the postmaster running locally
>         and accepting connections on Unix socket '/tmp/.s.PGSQL.0'?

Hmm, do you have an environment definition for PGPORT?

I notice that pg_regress.sh contains

    export PGPORT

but it doesn't necessarily set any value for PGPORT.  It seems possible
that some shells may take this as license to invent an empty-string
value for PGPORT, which would cause libpq to think that port 0 is being
specified.

My feeling is that libpq ought to ignore an empty-string PGPORT
environment value, rather than treat it as selecting port 0.
Comments anyone?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Thomas T. Thai"
Date:
Subject: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]
Next
From: "Thomas T. Thai"
Date:
Subject: Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]