Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 79DB56326F8 for ; Tue, 27 Oct 2009 09:51:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15318-09 for ; Tue, 27 Oct 2009 12:51:50 +0000 (UTC) X-Greylist: delayed 00:11:04.231938 by SQLgrey-1.7.6 Received: from a2s36.a2hosting.com (a2s36.a2hosting.com [74.126.18.130]) by mail.postgresql.org (Postfix) with ESMTP id C84FE6326C2 for ; Tue, 27 Oct 2009 09:51:50 -0300 (ADT) Received: from adsl-70-101-72.tys.bellsouth.net ([98.70.101.72] helo=[192.168.1.18]) by a2s36.a2hosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1N2lWW-0003kt-58; Tue, 27 Oct 2009 08:51:40 -0400 Subject: Re: Implementing Frontend/Backend Protocol TCP/IP Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: John DeSoi In-Reply-To: Date: Tue, 27 Oct 2009 08:51:39 -0400 Cc: "John R Pierce *EXTERN*" , "Alvaro Herrera" , "Raimon Fernandez" , Content-Transfer-Encoding: 7bit Message-Id: <35DCEEAC-C98D-47A9-8C37-1953CEEB8282@pgedit.com> References: <92781008-8A70-42CE-A49B-6EE67103FACB@montx.com> <20091026231516.GN8812@alvh.no-ip.org> <4AE62E21.7040600@hogranch.com> To: Albe Laurenz X-Mailer: Apple Mail (2.1076) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s36.a2hosting.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - pgedit.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200910/1027 X-Sequence-Number: 154721 On Oct 27, 2009, at 4:55 AM, Albe Laurenz wrote: > That's probably not the problem in the original message, but there > are things you can do with the frontend/backend protocol that libpq > does not expose: for example, with the extended query protocol you can > send a "Bind" call that requests that some of the results should be > returned in text format, others in binary. Another protocol feature that I don't think is exposed in libpq is the ability to limit the maximum number of rows returned by a query. So if you are executing end user queries, you don't have to worry about processing a massive result set or somehow parsing the query to add a limit clause. John DeSoi, Ph.D.