Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Larry Rosenman" <ler@lerctr.org>
Cc: "'Larry Rosenman'" <lrosenman@pervasive.com>, "'PostgreSQL Hackers List'" <pgsql-hackers@postgresql.org>
Date: 2006-03-29T03:59:46Z
Lists: 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