| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Thomas T(dot) 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] |
| Date: | 2000-12-31 01:10:58 |
| Message-ID: | 4233.978225058@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
"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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas T. Thai | 2000-12-31 01:57:59 | Re: NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch] |
| Previous Message | Thomas T. Thai | 2000-12-31 00:39:23 | NetBSD/Alpha and PostgreSQL-current [was Re: NetBSD/Alpha and rkirkpat's patch] |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Kientzle | 2000-12-31 01:11:26 | Re: Failed Statements within Transactions |
| Previous Message | Courtney Thomas | 2000-12-31 01:08:33 | pgaccess |