Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?
Date
Msg-id 8269.1143604786@sss.pgh.pa.us
Whole thread Raw
In response to Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?  ("Larry Rosenman" <ler@lerctr.org>)
Responses Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?  ("Larry Rosenman" <ler@lerctr.org>)
Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?  (Jeremy Drake <pgsql@jdrake.com>)
List pgsql-hackers
"Larry Rosenman" <ler@lerctr.org> writes:
> 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.

[ shrug... ]  So?  There isn't going to be any way that
random-app-using-libpq is going to have a way to tell the user what the
underlying copy of libpq is using for this default --- adding a call for
that will be nothing more nor less than a waste of code space.  You'd be
best off running strings(1) over the libpq.so file when the question
comes up.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Larry Rosenman"
Date:
Subject: Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?
Next
From: "Larry Rosenman"
Date:
Subject: Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?