X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A94A7DB98A for ; Thu, 17 Nov 2005 16:39:02 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 14236-08 for ; Thu, 17 Nov 2005 20:39:02 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 9BC8ADB90A for ; Thu, 17 Nov 2005 16:38:59 -0400 (AST) Received: from [10.30.1.23] ([72.16.194.3]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id jAHKXqkO007553; Thu, 17 Nov 2005 12:33:53 -0800 Message-ID: <437CEAC2.6050001@commandprompt.com> Date: Thu, 17 Nov 2005 12:40:34 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: David Rysdam CC: pgsql-interfaces@postgresql.org Subject: Re: Not clear on what PQgetResult does References: <437CD359.5080908@ll.mit.edu> <451.1132256298@sss.pgh.pa.us> <437CE1B0.3040001@ll.mit.edu> In-Reply-To: <437CE1B0.3040001@ll.mit.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Thu, 17 Nov 2005 12:33:53 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/43 X-Sequence-Number: 5839 > >> >> It isn't. You can use it in an asynchronous client, but the way you do >> that is by not calling it until PQisBusy says you can (which means the >> whole result has arrived, and you're just calling PQgetResult to get >> hold of it). >> > So there's no way to have libpq return partial results before they are > all ready? > > If I may, I would like to express some degree of incredulity. Even > the version of Sybase I'm using does this right and it's from 1997! I am sure we would welcome a patch ;)) Sincerely, Joshua D. Drake > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match