Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA75116 for ; Wed, 15 Sep 1999 09:54:06 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA19075; Wed, 15 Sep 1999 09:53:03 -0400 (EDT) To: Clayton Cottingham cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] to do's? In-reply-to: Your message of Tue, 14 Sep 1999 14:53:37 -0700 <37DEC3E1.59071869@smartt.com> Date: Wed, 15 Sep 1999 09:53:02 -0400 Message-ID: <19073.937403582@sss.pgh.pa.us> From: Tom Lane Clayton Cottingham writes: > hi i was wondering if multi threading will be enabled soon? Huh? We already have multiple backends, what advantage would there be to using threads? > is that i have a 1.3 mil row db when i try to select all i get memory > out type errors, either system wide or droping the backend The problem is probably at the application end --- libpq is built on the model that it can collect the entire query result in memory and then give the application random access to that array. So if the query result won't fit in the space available to the application, trouble. I don't see why this would affect anything else in your system, though, unless the app uses up all available swap space and holds it for a while before crashing... What you probably want to do instead of a straight SELECT is use DECLARE CURSOR and FETCH to retrieve the table a few dozen/hundred rows at a time. regards, tom lane