agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: sdalby@fuller.mech.utah.edu
To: postgres@postgres.Berkeley.EDU
Subject: Postgres 4.2 Problems...
Date: Thu, 18 Aug 1994 10:13:38 -0600
Message-ID: <199408181613.AA18993@fuller.mech.utah.edu> (raw)

Hello there,

We have five small Postgres databases against which we pose "randomly"
generated queries nightly.  Under SunOS 4.1.1 and Postgres version
4.0.1 we were able to pose greater than 10,000 queries without any
Postgres problems.  Now under Solaris 2.3 and Postgres 4.2 we are only
able to get about 3,000 before the ~postgres/data/pg_log file
(relation) balloons to 134 MB (the file is *extremely* sparse) and we
get the error:

WARN:Aug 15 10:17:08:cannot open segment 1 of relation pg_time

At this point we are not able to do any more with Postgres and our
homegrown solution is to use ~postgres/bin/cleardbdir,
~postgres/bin/initdb, and rebuild the five small databases.

As an experiment, we have also built Postgres 4.2 under SunOS 4.1.1.
Different problem here (the Postgres backend dies), but we are still
unable to get through as many queries as we were able to under version
4.0.1 of Postgres.  In fact, the number of queries we are able to
process is similar to the number processed under Solaris 2.3.

Both versions passed the regression test when I built them.  Has
anyone else experienced problems similar to this? 

       Sean Dalby
       Department of Mechanical Engineering Design Systems Laboratory
       University of Utah
       sdalby@part.net

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================

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 using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Cc: sdalby@fuller.mech.utah.edu
  Subject: Re: Postgres 4.2 Problems...
  In-Reply-To: <199408181613.AA18993@fuller.mech.utah.edu>

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

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