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

i concure with this.

On Sat, 30 Dec 2000, Tom Lane wrote:

> Date: Sat, 30 Dec 2000 20:10:58 -0500
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: Thomas T. Thai <tom(at)minnesota(dot)com>
> Cc: pgsql-bugs(at)postgresql(dot)org, Brent Verner <brent(at)rcfile(dot)org>,
> Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net>,
> Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>,
> Arrigo Triulzi <arrigo(at)albourne(dot)com>
> Subject: Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha
> and rkirkpat's patch]
>
> "Thomas T. Thai" <tom(at)minnesota(dot)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
>