Skip site navigation (1) Skip section navigation (2)

Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Larry Rosenman" <ler(at)lerctr(dot)org>
Cc: "'Larry Rosenman'" <lrosenman(at)pervasive(dot)com>, "'PostgreSQL Hackers List'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?
Date: 2006-03-29 03:59:46
Message-ID: 8269.1143604786@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Larry Rosenman" <ler(at)lerctr(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Larry RosenmanDate: 2006-03-29 04:02:39
Subject: Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?
Previous:From: Larry RosenmanDate: 2006-03-29 03:37:13
Subject: Re: Exposing DEFAULT_PGSOCKET_DIR via a libpq function?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group