Date: Tue, 19 Aug 2014 12:12:21 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>,
 PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: PQgetssl() and alternative SSL implementations
Message-ID: <20140819161221.GI16422@tamriel.snowman.net>
References: <53F1E989.8020609@vmware.com>
 <20140819144841.GA16422@tamriel.snowman.net>
 <53F36B6E.6040105@vmware.com>
 <20140819154436.GD16422@tamriel.snowman.net>
 <20140819161000.GF6817@eldon.alvh.no-ip.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="9m7PSxAMKS61vLzQ"
Content-Disposition: inline
In-Reply-To: <20140819161000.GF6817@eldon.alvh.no-ip.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--9m7PSxAMKS61vLzQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Alvaro Herrera (alvherre@2ndquadrant.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.
>=20
> 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

--9m7PSxAMKS61vLzQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJT83dlAAoJEO1sijiDR2RVpGsP/juKw1wO7o6qhUS1ugvkN/Ji
8A5h4oBNmp/gD7KRZrSRUsj1M8JlYrXbld9NI+lgS13w3f43YFKD12uLEVdks8ZB
bJtSk1zDxpGPh/RQhSx4XlAcAasKoPhSVO+c0cHUUXf6GnadydlzOp7KaOJcM0GJ
hvVA+f1WSacpB1pIsFYLRTyi3oBNHf2AVSUBzZVT0rypRe2geehwnuk5iZ7dyJ/c
yAnnSv2OyJx7jsJX30dBqz/xIxG/Y48+Dj0Jz3MM6mMKobxMtrWsUpq2WKN07fFj
UL9YtubvGYFQDGEODx3Y2e4L40T3792PbZjpSUIw75uRGq6fW8T/a7c2jvQ8TLmh
w+qmfu70s2H0bG9aC0H+i74+D9P7A5zgmk1hXF1vvbSyG1LKFO6kpza1htfWaz9U
VQoVhbrbmXfs4hhCFPR4ywvKmxvV7ID+n0Fe6yQEjIsrpmZXgRu8l3Zb2G/BfdAd
KkAI323yHJdm93U82kduo/2YWVbaRameWUK903bL6aeTn4W7VtF/WF/xyDVPiodk
uohbouikM5wsJNZh7F7LNVGOeMpRpWJa10qek87HysUZGj/WqFSIiQwt+y+9sL3U
Qo9f3fLxIqD2g0v/qB7bKym4GpfWt53c0xEuR3OinrxndPuQQFRtDoHfqBD11iJO
VqqrM+iypUlj0BIPftNr
=DUao
-----END PGP SIGNATURE-----

--9m7PSxAMKS61vLzQ--