Re: PHP's pg_connect() and non-standard location of the socket (was: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432)

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arcady Genkin <a.genkin@utoronto.ca>
Cc: Postgres-general <pgsql-general@postgresql.org>
Date: 2001-06-12T21:39:51Z
Lists: pgsql-bugs, pgsql-general
Arcady Genkin <a.genkin@utoronto.ca> writes:
>> They're not, unless you tell them, which is why runtime setting of the
>> parameter isn't all that useful IMHO.  But some people wanted it, so
>> there it is.

> Hmm...  How would I tell that to `psql'?  Via "-v" parameter?

IIRC, a hostname parameter that starts with '/' is now interpreted as
a socket path.  So you'd do psql -h /path/to/something, or set PGHOST,
to inform the client about a nonstandard socket location.

$ psql -h /nowhere -p 7654
psql: connectDBStart() -- connect() failed: No such file or directory
        Is the postmaster running locally
        and accepting connections on Unix socket '/nowhere/.s.PGSQL.7654'?

			regards, tom lane