Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 294F74760B7 for ; Thu, 26 Sep 2002 23:15:35 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 9892F475EDF for ; Thu, 26 Sep 2002 23:15:34 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g8R3FYhR020426; Thu, 26 Sep 2002 23:15:34 -0400 (EDT) To: Stephan Szabo Cc: jonesbl@WellsFargo.COM, pgsql-sql@postgresql.org Subject: Re: FW: query problem "server sent binary data ... without In-reply-to: <20020926160003.H30444-100000@megazone23.bigpanda.com> References: <20020926160003.H30444-100000@megazone23.bigpanda.com> Comments: In-reply-to Stephan Szabo message dated "Thu, 26 Sep 2002 16:01:53 -0700" Date: Thu, 26 Sep 2002 23:15:33 -0400 Message-ID: <20425.1033096533@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/350 X-Sequence-Number: 9627 Stephan Szabo writes: > On Thu, 26 Sep 2002 jonesbl@WellsFargo.COM wrote: >> the query runs for 10 minutes or so, then outputs: > How much data is that sending? The client library is going to try to > buffer the entire result set. And, in fact, this is the typical behavior when it runs out of memory for the result set :-( ... it loses track of the fact that it was receiving a result set at all, and starts spitting out complaints that it's not in the right state as it receives subsequent rows. (That should be fixed someday, but no one's got round to it.) Consider using a cursor so you can FETCH a reasonable number of rows at a time. regards, tom lane