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

Thomas T. Thai <tom@minnesota.com>

From: "Thomas T. Thai" <tom@minnesota.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org, Brent Verner <brent@rcfile.org>, Ryan Kirkpatrick <pgsql@rkirkpat.net>, Adriaan Joubert <a.joubert@albourne.com>, Arrigo Triulzi <arrigo@albourne.com>
Date: 2000-12-31T01:57:59Z
Lists: pgsql-bugs, pgsql-general
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@sss.pgh.pa.us>
> To: Thomas T. Thai <tom@minnesota.com>
> Cc: pgsql-bugs@postgresql.org, Brent Verner <brent@rcfile.org>,
>      Ryan Kirkpatrick <pgsql@rkirkpat.net>,
>      Adriaan Joubert <a.joubert@albourne.com>,
>      Arrigo Triulzi <arrigo@albourne.com>
> Subject: Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha
>     and rkirkpat's patch] 
> 
> "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
>