> -----Original Message----- > From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED] > Sent: 13 April 2006 11:54 > To: Dave Page; pgsql-hackers@postgresql.org; Hiroshi Inoue > Subject: Re: [HACKERS] Practical impediment to supporting > multiple SSL libraries > > On Thu, Apr 13, 2006 at 06:44:12AM -0400, Stephen Frost wrote: > > Instead of having it hijack the libpq connection and implement the > > wireline protocol itself, why don't we work on fixing the problems > > (such as the double-copying that libpq requires) in libpq > to allow the > > driver (and others!) to use it in the 'orthodox' way? > > Ok. I'm not sure what this "double copying" you're referring > to is,
The libpq driver copies results out of the PGresult struct into the internal QueryResult classes. With libpq out of the loop, data can go straight from the wire into the QR. > but I'd certaintly like to know why people are > reimplementing the protocol (psqlODBC is hardly the only one). There are elements of the wire protocol that libpq doesn't actually implement from what I recall. IIRC, they were added specifically for JDBC but also intended to be used by psqlODBC as well. I forget the details though as I wasn't so involved with the ODBC development back then. In addition of course, implementing the protocol natively does allow for maximum flexibility. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
