Re: BUG #6171: Sockets Issue

"Robert Hopek" <rhopek(at)getnetworks(dot)com> writes:
> Why do you have the configuration option to change the pgsql socket (which
> we need to do for our jailed shell environment), but not have psql check the
> postgresql.conf file for the enablement of that location change so that psql
> would look there automatically?

How would that work? psql does not know where the server configuration
file is, and would typically not have adequate permissions to read it
anyway.

If you must use a socket location other than /tmp, the most comfortable
way to deal with it is to build custom executables with the correct
locations as their wired-in defaults. This is not really much different
from the situation for a custom port number...

> It seems very counter-productive.

A common reason for using a nondefault connection location is to not
*want* the postmaster to be reached by default-using clients. The
configuration file option does have use-cases, just not yours.

regards, tom lane