| From: | "Larry Rosenman" <lrosenman(at)pervasive(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:33:50 |
| Message-ID: | F6616E0E81AC0841B1F9DD252F7C4B55041A79@ausmaildd.aus.pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "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.
It still gets into the messiness of pg_config doesn't load libpq, and
there could be a mis-match.
--
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 | Simon Riggs | 2006-05-17 17:38:47 | Re: [PATCH] Compression and on-disk sorting |
| Previous Message | Tom Lane | 2006-05-17 17:29:05 | Re: [GENERAL] Querying libpq compile time options |