Tom Lane wrote: > "Larry Rosenman" <ler@lerctr.org> writes: >> Tom Lane wrote: >>> pg_config would seem to be the appropriate place, not libpq nor >>> psql. > >> The issue is what psql (and any libpq using program) is going to use >> to find the UNIX socket. > > No, the issue is where the server put the socket. libpq is the wrong > place because libpq is not the only thing people use to connect to > the server. > > If the DBA sets a non-default unix_socket_directory via > postgresql.conf then you're screwed no matter what: no client-side > code can hope to tell you where it is. The only thing that is useful > to inspect is the server's compile-time default, and pg_config is the > right mechanism to inspect that with. > > regards, tom lane
The other issue is borked installs where the server and libpq disagree. What I'm looking for is to expose what libpq has for it's default as well as what the server is using. There is currently no way to determine what libpq has for it's default. What happened in the irc case was a partial re-install with non-matching server and libpq. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3683 US ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
