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 18:31:50 |
Message-ID: | 200605171831.k4HIVoM14007@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Larry Rosenman wrote:
> 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.
That is the administrator's job, to make sure they match. Applications
programmers can't do that.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-05-17 18:38:04 | Re: [GENERAL] Querying libpq compile time options |
Previous Message | Bruce Momjian | 2006-05-17 18:31:17 | Re: [GENERAL] Querying libpq compile time options |