| From: | "Larry Rosenman" <lrosenman(at)pervasive(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, <spaminos-sql(at)yahoo(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Querying libpq compile time options |
| Date: | 2006-05-17 17:05:56 |
| Message-ID: | F6616E0E81AC0841B1F9DD252F7C4B55041A75@ausmaildd.aus.pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(dot)Rosenman(at)pervasive(dot)com
Web: www.pervasive.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-17 17:08:27 | Re: [GENERAL] Querying libpq compile time options |
| Previous Message | Greg Stark | 2006-05-17 17:01:11 | Re: Compression and on-disk sorting |