From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Hiroshi Inoue" <inoue(at)tpf(dot)co(dot)jp> |
Subject: | Re: Practical impediment to supporting multiple SSL libraries |
Date: | 2006-04-12 16:25:47 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9C66@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Martijn van Oosterhout [mailto:kleptog(at)svana(dot)org]
> Sent: 12 April 2006 17:15
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Practical impediment to supporting
> multiple SSL libraries
>
> On Wed, Apr 12, 2006 at 05:03:32PM +0100, Dave Page wrote:
>
> <about the declaration of PQgetssl>
> > The next version of psqlODBC (that has just gone into CVS tip after
> > months of work and debate) uses it, and would break almost
> completely
> > should it be removed, therefore any backwards incompatible change
> > should be avoided imho. And 2 or 4 could cause chaos for
> Windows users
> > if different DLL builds get mixed up.
>
> Hmm, may I ask what it uses it for? Just to get information,
> or something more substantial?
The driver implements all versions of the wire protocol itself, but if
libpq is available at runtime (it will dynamically load it on platforms
that support it) it can use it for connection setup so features like SSL
can be provided easily. I'm still not overly familiar with how it works
yet, but I'm sure Hiroshi (CC'd) can provide further details if you need
them.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-12 16:32:01 | Re: Practical impediment to supporting multiple SSL libraries |
Previous Message | Greg Sabino Mullane | 2006-04-12 16:22:15 | Re: Get explain output of postgresql in Tables |