Re: Practical impediment to supporting multiple SSL libraries - Mailing list pgsql-hackers

From Zeugswetter Andreas DCP SD
Subject Re: Practical impediment to supporting multiple SSL libraries
Date
Msg-id E1539E0ED7043848906A8FF995BDA579F31339@m0143.s-mxs.net
Whole thread Raw
In response to Practical impediment to supporting multiple SSL libraries  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Practical impediment to supporting multiple SSL libraries  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
> Well, the psqlODBC driver apparently ran into a number of problems
with
> libpq that resulted in them not using it for their purpose.
> Given libpq primary purpose is to connect to PostgreSQL, it failing at
that is
> something that should be fixed.

I think you are forgetting, that e.g. a JDBC driver will not want to
depend on
an external C dll at all. It will want a native Java implementation
(Group 4).
Thus imho it is necessary to have a defined wire protocol, which we
have.

So if a driver needs to use the wire protocol it is imho not a problem.
If applications started using it, because they don't find a suitable
driver,
now that would be a problem.

Andreas


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: OS cached buffers (was: Support Parallel Query Execution
Next
From: Greg Stark
Date:
Subject: Re: Practical impediment to supporting multiple SSL libraries