Re: Practical impediment to supporting multiple SSL libraries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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-13 15:52:28
Message-ID: 20600.1144943548@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> ...you seem to be suggesting that all the data be stored in one big memory
> block at resultset.

I didn't like that either; it assumes far too much about what the
application needs to do. I think what's wanted is a callback hook
that lets the app decide where and how to store the data. Not sure
what the hook's API should be exactly, though.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2006-04-13 15:54:33 Re: Practical impediment to supporting multiple SSL libraries
Previous Message Tom Lane 2006-04-13 15:34:14 Re: two-argument aggregates and SQL 2003