| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Mark Hellegers <mark(at)firedisk(dot)net>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Compiling without libpq |
| Date: | 2015-06-15 18:44:50 |
| Message-ID: | 557F1D22.9060803@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 06/15/2015 11:27 AM, Mark Hellegers wrote:
>
> Hello,
>
> what is the difference in compiling with or without libpq?
As I recall you lose extended auth capability (no ldap for example) and
you lose the ability to have encrypted connections.
> I see in configure script that openssl is disabled if I compile without
> libpq. Why is that and what functionality do I loose exactly?
See my comment about encrypted connections above.
JD
>
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-06-16 00:11:04 | Re: Compiling without libpq |
| Previous Message | Mark Hellegers | 2015-06-15 18:27:27 | Compiling without libpq |