Re: PHP's pg_connect() and non-standard location of the socket (was: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432)
Arcady Genkin <a.genkin@utoronto.ca>
From: Arcady Genkin <a.genkin@utoronto.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Postgres-general <pgsql-general@postgresql.org>
Date: 2001-06-14T17:02:58Z
Lists: pgsql-bugs, pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> writes: > 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'? Cool! Thanks a lot. Just changed the location of the socket to /var/run, and my PHP script was able to connect using "host=/var/run" string. Thanks very much once more. -- Arcady Genkin i=1; while 1, hilb(i); i=i+1; end