pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steven M. Wheeler <swheeler@sabre.com>
To: pgsql-sql@hub.org
Subject: Re: pgsql-sql-digest V1 #225
Date: Fri, 14 May 1999 13:22:58 -0500
Message-ID: <373C6A02.78101BF@sabre.com> (raw)
References: <199905120300.XAA19901@hub.org>

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





view thread (7+ messages)  latest in thread

Message-ID: <373C6A02.78101BF@sabre.com>
Permalink:  ../373C6A02.78101BF@sabre.com/
Also on:    postgresql.org/message-id/373C6A02.78101BF@sabre.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: swheeler@sabre.com, pgsql-sql@hub.org
  Subject: Re: pgsql-sql-digest V1 #225
  In-Reply-To: <373C6A02.78101BF@sabre.com>
  References: <199905120300.XAA19901@hub.org> <373C6A02.78101BF@sabre.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox