Tom Lane wrote: > "Larry Rosenman" <[EMAIL PROTECTED]> writes: >> 1) expose DEFAULT_PGSOCKET_DIR via a libpq call >> 2) add this information to the psql --version output (or some other >> switch, I'm agnostic). > > pg_config would seem to be the appropriate place, not libpq nor psql.
The issue is when you overwrite PIECES of an install, and their inconsistent. I want to put it in libpq, since that is what makes the connection to the server. pg_config doesn't link to libpq at all. The issue is what psql (and any libpq using program) is going to use to find the UNIX socket. we have the unix_socket_directory GUC, but that doesn't show the DEFAULT_PGSOCKET_DIR that libpq is using, and in fact there is no where that the server exposes it's default, either. I'm wondering if we should expose it's default in unix_socket_directory when the config doesn't set it. 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-3893 ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
