From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: PQgetssl() and alternative SSL implementations |
Date: | 2014-08-19 16:12:21 |
Message-ID: | 20140819161221.GI16422@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> Stephen Frost wrote:
> > Yeah, that's what I remembered. There was an attempt to make that
> > change at one point, but it was reverted due to the lack of batching
> > ability in libpq (without resorting to cursors, as I recall...),
> > requiring double the memory usage. Still, if pqsecure_read and
> > pqsecure_write are sufficient to make the ODBC driver work, that's good
> > news. I had been worried it did other things with the OpenSSL struct
> > beyond just using those.
>
> Um, libpq has recently gained the ability to return result fragments,
> right? Those didn't exist when libpq-ification of odbc was attempted,
> as I recall -- perhaps it's possible now.
I was trying to remember off-hand if we still had that or not.. I
thought there was discussion about removing it, actually, but perhaps
that was something else.
I agree that having that would definitely help with the ODBC driver.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-08-19 16:14:38 | Re: PQgetssl() and alternative SSL implementations |
Previous Message | Stephen Frost | 2014-08-19 16:11:07 | Re: PQgetssl() and alternative SSL implementations |