On Mon, Aug 18, 2014 at 7:54 AM, Heikki Linnakangas <hlinnakan...@vmware.com> wrote: > In order to support alternatives to OpenSSL, we need to wean off > applications from using PQgetssl(). To do that, we have to provide an > alternative API to get the same information. PQgetSSL() returns a pointer > directly to the OpenSSL private struct, and you can do anything with that. > We cannot have a generic interface that exposes everything, so we need to > identify the information that people actually want, and expose that.
I have a hard time believing that something like this will really satisfy anyone. Why not just add PQgetSchannelHandleOrWhatever() and call it good? We can try to be incredibly thorough in exposing the information people want and we will still inevitably miss something that someone cares about; worse, we'll spend an awful lot of time and energy along the way. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers