Re: [GENERAL] Querying libpq compile time options

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:16:07
Message-ID: 21418.1147886167@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:
> I had made a proposal to expose the path used for pg_service.conf.

I don't remember that anymore, but my question about it would be "what's
the use case?" I don't see a particularly good reason why an app would
need to know that, whereas it's pretty clear why a thread-dependent app
might wish to defend itself against a thread-unsafe libpq.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-05-17 17:17:57 Re: [GENERAL] Querying libpq compile time options
Previous Message Bruce Momjian 2006-05-17 17:15:54 Re: [GENERAL] Querying libpq compile time options