Re: [GENERAL] Querying libpq compile time options
От | Bruce Momjian |
---|---|
Тема | Re: [GENERAL] Querying libpq compile time options |
Дата | |
Msg-id | 200605171708.k4HH8RS26243@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [GENERAL] Querying libpq compile time options ("Larry Rosenman" <lrosenman@pervasive.com>) |
Ответы |
Re: [GENERAL] Querying libpq compile time options
|
Список | pgsql-hackers |
Larry Rosenman wrote: > 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? 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. +
В списке pgsql-hackers по дате отправления: