Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch]
От | Thomas T. Thai |
---|---|
Тема | Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch] |
Дата | |
Msg-id | Pine.NEB.4.21.0012301957530.19799-100000@ns01.minnesota.com обсуждение исходный текст |
Ответ на | Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch] (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
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 >
В списке pgsql-bugs по дате отправления: