Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?

"Larry Rosenman" <ler(at)lerctr(dot)org> writes:
> What's the harm of a (pseudo code):

> const char *PQgetunixsocketdir(void)
> {
> return(DEFAULT_PGSOCKET_DIR)
> }

> In libpq, and a psql command line switch to call it.

By the time you get done adding the infrastructure and documentation for
those two layers of features, you're talking about many hundreds of
lines of stuff, not four. There are also definitional issues (what does
this do on platforms without Unix sockets) and future proofing (will we
always have DEFAULT_PGSOCKET_DIR). So "what's the harm" is not the
appropriate measure --- especially when this proposal clearly doesn't
help in a lot of the scenarios in which one might wish to know the
information.

regards, tom lane