| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Larry Rosenman" <lrosenman(at)pervasive(dot)com> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(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:29:05 |
| Message-ID: | 21614.1147886945@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Larry Rosenman" <lrosenman(at)pervasive(dot)com> writes:
>> Uh, it is an _admin_ function, not an application programmer
>> function.
> but libpq is the only thing that knows where it is, and I had proposed a
> way for psql to use the function to get it.
It'd make more sense for pg_config to expose this as one of the
available information bits. The difference from the thread-support
case is that you'd typically want to get the pg_service.conf location
manually, and that's exactly what pg_config is designed for. Verifying
thread support, on the other hand, is something that a program would
want to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2006-05-17 17:33:50 | Re: [GENERAL] Querying libpq compile time options |
| Previous Message | Tom Lane | 2006-05-17 17:25:43 | Re: PL/pgSQL 'i = i + 1' Syntax |