Re: [PATCH] Automatic client certificate selection support for libpq v1 - Mailing list pgsql-hackers

From Seth Robertson
Subject Re: [PATCH] Automatic client certificate selection support for libpq v1
Date
Msg-id 200905111644.n4BGi0Px003031@no.baka.org
Whole thread Raw
In response to Re: [PATCH] Automatic client certificate selection support for libpq v1  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
In message <20090511144317.GC8689@alvh.no-ip.org>, Alvaro Herrera writes:
   Magnus Hagander wrote:      > Another thought: if we were to make ourselves support multiple SSL   > libraries (that
hasbeen suggested before - at that point, people wanted   > GnuTLS), we could also add support for Windows SChannel,
whichI'm sure   > some win32 people would certainly prefer - much easier to do SSL   > deployments within an existing
MSinfrastructure...      If we were to support multiple libraries, would they be selected at run   time or compile
time? If only compile time, how would it work for the   Windows installer with the SChannel thingy --- would they have
to  distribute two separate packages, for OpenSSL and SChannel?
 

While I have successfully performed runtime conditional dynamic
loading inside programs (each shared library with its own list of
dependent libraries) on one platform with one selected dynamic loading
API, I cannot say I recommend it.  This would aid neither portability,
debug-ability, or performance (though compared to the overhead of SSL,
the jump table is kinda irrelevant).
                -Seth Robertson                 in-pgsql-hackers@baka.org


pgsql-hackers by date:

Previous
From: Seth Robertson
Date:
Subject: Re: [PATCH] Automatic client certificate selection support for libpq v1
Next
From: Tom Lane
Date:
Subject: DROP TABLE vs inheritance