| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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:25:20 |
| Message-ID: | 31226.1408465520@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
>> 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.
Sure,
http://www.postgresql.org/docs/devel/static/libpq-single-row-mode.html
That's a done deal, it won't be going away.
Whether it would solve ODBC's problem I don't know (and I'm not
volunteering to do the work ;-))
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-08-19 16:29:50 | Re: PQgetssl() and alternative SSL implementations |
| Previous Message | Heikki Linnakangas | 2014-08-19 16:22:39 | Re: PQgetssl() and alternative SSL implementations |