Peter Eisentraut wrote:
> Lamar Owen writes:
> > But, let me ask this: is it a good thing for PostgreSQL clients to have
> > hard-coded socket locations? (Good thing or not, it exists already, and
> > I know it does....)
> Perhaps there could be some sort of /etc/postgresql.conf file that is read
> by both client and server that can control these sort of aspects. But I
> don't see much use in it besides port number and socket location.
> Because those are, by definition, the only parameters in common to client
> and server.
Of course, -i and TCP/IP to localhost obviate all of this.
How about an environment variable? PGSOCKLOC? Use the hard-coded
default if the envvar not set? This way multiple postmasters running on
multiple sockets can be smoothly supported.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
