Received: from mx1.sabre.com (mx1.sabre.com [199.100.49.110]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA38477 for ; Fri, 14 May 1999 14:28:25 -0400 (EDT) (envelope-from swheeler@sabre.com) Received: (from mailer@localhost) by mx1.sabre.com (8.9.3/8.9.0) id NAA02065 for ; Fri, 14 May 1999 13:27:54 -0500 (CDT) Received: from (pop3.sabre.com [144.9.112.62]) by mx1.sabre.com via smap (V2.1) id xma002042; Fri, 14 May 99 13:27:36 -0500 Received: from sabre.com ([172.29.63.42]) by pop3.sabre.com (Netscape Messaging Server 3.6) with ESMTP id AAA6946 for ; Fri, 14 May 1999 13:27:34 -0500 Message-ID: <373C6A02.78101BF@sabre.com> Date: Fri, 14 May 1999 13:22:58 -0500 From: "Steven M. Wheeler" Organization: The SABRE Group, UNIX Engineering X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@hub.org Subject: Re: pgsql-sql-digest V1 #225 References: <199905120300.XAA19901@hub.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Two problems, one question: First my configuration: I have a 350MB+ DB with two tables in it. One of the tables contains 2.5M+ rows, the other is empty. I have 1 index on the table with rows in it. This is all running on a Compaq 450MHz Pentium II with 256MB RAM, 1GB of swap. The DB is on its own 6GB EIDE drive. Problem #1: Using psql in interactive mode, I issue "select count(*) from currnt;". The postmaster starts to read data in, as seen in vmstat by the bi stat jumping sharply. Very rapidly, CPU goes to 0% idle, postmaster is using 99.4%, bi stat runs about 12K for 60-80 seconds, and then goes to 0, and everything stays there. I never get a return and the system stays maxed. When the row count in this table was below 2M, I would get a return count. Problem #2: Running psql in interactive mode, I issue "select * from currnt where cast(statdate as text) like '03-%-1999);". This runs for quite awhile, eats into swap to the tune of 670MB+ and then bombs out with a palloc error. After reading one of the FAQs, I first set ulimit -d to 65535, and then set it to unlimited. No change, still bombed out. The question: Am I trying to run too large a DB? Have I exceeded the capabilities of Postgres in its current incarnation? Have I got a hope in hell of getting this to work? I have already spent many, many, many, too many hours on these problems. Thanks -- Steven M. Wheeler UNIX Engineering The SABRE Group (918) 292-4119 (918) 292-4165 FAX