Re: [GENERAL] Querying libpq compile time options - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [GENERAL] Querying libpq compile time options
Date
Msg-id 200605171831.k4HIVoM14007@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] Querying libpq compile time options  ("Larry Rosenman" <lrosenman@pervasive.com>)
List pgsql-hackers
Larry Rosenman wrote:
> Tom Lane wrote:
> > "Larry Rosenman" <lrosenman@pervasive.com> writes:
> >>> Uh, it is an _admin_ function, not an application programmer
> >>> function.
> > 
> >> but libpq is the only thing that knows where it is, and I had
> >> proposed a way for psql to use the function to get it.
> > 
> > It'd make more sense for pg_config to expose this as one of the
> > available information bits.  The difference from the thread-support
> > case is that you'd typically want to get the pg_service.conf location
> > manually, and that's exactly what pg_config is designed for. 
> > Verifying thread support, on the other hand, is something that a
> > program would want to do.
> 
> It still gets into the messiness of pg_config doesn't load libpq, and
> there could be a mis-match.

That is the administrator's job, to make sure they match.  Applications
programmers can't do that.

--  Bruce Momjian   http://candle.pha.pa.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Querying libpq compile time options
Next
From: Andrew Dunstan
Date:
Subject: Re: [GENERAL] Querying libpq compile time options