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