Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 484C09FBD8A for ; Thu, 22 Feb 2007 07:02:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 56758-01 for ; Thu, 22 Feb 2007 07:02:16 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from grassmarket.ucs.ed.ac.uk (grassmarket.ucs.ed.ac.uk [129.215.166.64]) by postgresql.org (Postfix) with ESMTP id 1D05D9FBE8E for ; Thu, 22 Feb 2007 07:02:19 -0400 (AST) Received: from [129.215.2.130] (dhcp-2-130.inf.ed.ac.uk [129.215.2.130]) by grassmarket.ucs.ed.ac.uk (8.13.8/8.12.10) with ESMTP id l1MB2IcX007702 for ; Thu, 22 Feb 2007 11:02:18 GMT Subject: Disable result buffering to frontend clients From: Konstantinos Krikellas To: pgsql-performance Content-Type: text/plain Date: Thu, 22 Feb 2007 11:02:50 +0000 Message-Id: <1172142170.4718.13.camel@kkrik-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Edinburgh-Scanned: at grassmarket.ucs.ed.ac.uk with MIMEDefang 2.33, Sophie, Sophos Anti-Virus X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.45 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200702/228 X-Sequence-Number: 23282 Hi, I am trying to execute some queries in PostgreSQL that produce a large number of results and I do not want to display the output (redirect it to /dev/null). I have tried the psql client with \o /dev/null option, JDBC and libpq functions, but all of them have to buffer totally the result before redirecting it. Is there any way to disable result buffering, either on the client or on the server side? Note that the EXPLAIN ANALYSE does not produce consistent estimations as it seems to avoid calling the result tuple construction function. This is concluded by the fact that augmenting the projection width hardly changes the execution time, which is incompatible with the supplementary field copy cost. Thanks. Konstantinos Krikellas