Re: [GENERAL] Querying libpq compile time options

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Larry Rosenman <lrosenman(at)pervasive(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:08:27
Message-ID: 200605171708.k4HH8RS26243@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Larry Rosenman wrote:
> 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?

No idea, what is the URL of your proposal. Keep in mind this is not
option-specific.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2006-05-17 17:10:14 Re: [GENERAL] Querying libpq compile time options
Previous Message Larry Rosenman 2006-05-17 17:05:56 Re: [GENERAL] Querying libpq compile time options