X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 26562D1B8A1 for ; Mon, 18 Aug 2003 23:50:15 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 44934-02 for ; Mon, 18 Aug 2003 23:50:06 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 455DDD1B8B9 for ; Mon, 18 Aug 2003 23:50:02 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h7J2o65H019302; Mon, 18 Aug 2003 22:50:06 -0400 (EDT) To: Peter.Rupp@ual.com Cc: pgsql-interfaces@postgresql.org Subject: Re: Help with retrieving large results sets and memory usage. In-reply-to: References: Comments: In-reply-to Peter.Rupp@ual.com message dated "Mon, 18 Aug 2003 09:44:11 -0500" Date: Mon, 18 Aug 2003 22:50:06 -0400 Message-ID: <19301.1061261406@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/53 X-Sequence-Number: 4407 Peter.Rupp@ual.com writes: > When using either interface, I notice that when I select rows from a > table, it appears that the client interface retrieves the entire > results set at once...and loads it into memory on the client machine. The standard answer is to use a cursor and FETCH a few rows at a time. > Do you folks publish the network symantics and protocols used to > make sql requests and retrieve their results? http://developer.postgresql.org/docs/postgres/protocol.html regards, tom lane