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

From Larry Rosenman
Subject Re: [GENERAL] Querying libpq compile time options
Date
Msg-id F6616E0E81AC0841B1F9DD252F7C4B55041A75@ausmaildd.aus.pervasive.com
Whole thread Raw
Responses Re: [GENERAL] Querying libpq compile time options
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> I thought about this.  Attached is a patch you can use to
>> popen("pg_config") and then look for the thread flag to configure.
>> One idea would be to add this sample to our libpq documentation.  The
>> problem with the example is popen() overhead, pg_config not in
>> $PATH, or pg_config's version not matching libpq's version.
>
> Yeah, the last point seems like a killer objection :-(.  It'd be
> better to add some sort of libpq function to handle the issue.
>

and when I've proposed libpq functions to expose compile-time
constants, I've been shot down.

How is this different?


--
Larry Rosenman
Database Support Engineer

PERVASIVE SOFTWARE. INC.
12365B RIATA TRACE PKWY
3015
AUSTIN TX  78727-6531

Tel: 512.231.6173
Fax: 512.231.6597
Email: Larry.Rosenman@pervasive.com
Web: www.pervasive.com


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Compression and on-disk sorting
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Querying libpq compile time options