Received: from sss.pgh.pa.us ([216.151.103.158])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f35LcD892458
	for <pgsql-general@postgresql.org>; Thu, 5 Apr 2001 17:38:13 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f35Lc0w15640;
	Thu, 5 Apr 2001 17:38:00 -0400 (EDT)
To: "Hector Miranda" <hamg1@hotmail.com>
cc: pgsql-general@postgresql.org
Subject: Re: Problem with large tables 
In-reply-to: <LAW2-F8914eBa1kg3Am00000204@hotmail.com> 
References: <LAW2-F8914eBa1kg3Am00000204@hotmail.com>
Comments: In-reply-to "Hector Miranda" <hamg1@hotmail.com>
	message dated "Thu, 05 Apr 2001 20:56:48"
Date: Thu, 05 Apr 2001 17:38:00 -0400
Message-ID: <15637.986506680@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200104/264
X-Sequence-Number: 7345

"Hector Miranda" <hamg1@hotmail.com> writes:
> I'm working with Posgresql 7.0.3 on Red Hat linux 6.2. When I make the 
> following query "select * from mytable" (2000000 rows),

You're running out of application memory for the query result.  (libpq
doesn't recover from that too gracefully, unfortunately.)  Consider
using a cursor to fetch the data in more manageable chunks.

			regards, tom lane