Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJmE2-00031u-Rm for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Aug 2014 16:25:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XJmE2-0001PR-C0 for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Aug 2014 16:25:34 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XJmE1-0001PJ-6C for pgsql-hackers@postgresql.org; Tue, 19 Aug 2014 16:25:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XJmDt-0000dg-NY for pgsql-hackers@postgresql.org; Tue, 19 Aug 2014 16:25:31 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s7JGPKRg031227; Tue, 19 Aug 2014 12:25:20 -0400 From: Tom Lane To: Stephen Frost cc: Alvaro Herrera , Heikki Linnakangas , PostgreSQL-development Subject: Re: PQgetssl() and alternative SSL implementations In-reply-to: <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> <20140819161221.GI16422@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Tue, 19 Aug 2014 12:12:21 -0400" Date: Tue, 19 Aug 2014 12:25:20 -0400 Message-ID: <31226.1408465520@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Stephen Frost writes: > * Alvaro Herrera (alvherre@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers