From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | 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 16:59:13 |
Message-ID: | 21147.1147885153@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-patches |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John D. Burger | 2006-05-17 17:00:43 | Re: Why won't it index scan? |
Previous Message | Ed L. | 2006-05-17 16:37:32 | Why won't it index scan? |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-05-17 17:01:11 | Re: Compression and on-disk sorting |
Previous Message | Greg Stark | 2006-05-17 16:55:53 | Re: Compression and on-disk sorting |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-05-17 17:01:11 | Re: Compression and on-disk sorting |
Previous Message | Greg Stark | 2006-05-17 16:55:53 | Re: Compression and on-disk sorting |