Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with SMTP id MAA15571 for postgres-redist; Fri, 19 Aug 1994 12:43:20 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199408191943.MAA15571@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with SMTP id MAA15561; Fri, 19 Aug 1994 12:43:20 -0700
Message-Id: <199408191943.MAA15561@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
From: aoki@cs.berkeley.edu (Paul M. Aoki)
To: sdalby@fuller.mech.utah.edu
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: Postgres 4.2 Problems... 
Reply-To: aoki@cs.berkeley.edu (Paul M. Aoki)
In-reply-to: Your message of Thu, 18 Aug 1994 10:13:38 -0600 
	     <199408181613.AA18993@fuller.mech.utah.edu> 
Date: Fri, 19 Aug 94 12:43:19 -0700
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Fri, 19 Aug 94 12:43:20 -0700
Resent-XMts: smtp

sdalby@fuller.mech.utah.edu writes:
> 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) 

last night i ran 20000 insert/update/select statements against
one table on solaris 2.3 and sunos 4.1.3.  the log/time tables 
were exactly the size you would expect from 20000 committed 
transactions (one bit per xact in log, four bytes per xact in 
time, allocated in 8k pages):

bohemia:aoki (12)> ls -l $PGDATA/pg_{log,time}
-rw-------   1 postgres postgres    8192 Aug 19 06:27 /tmp/data/pg_log
-rw-------   1 postgres postgres   90112 Aug 19 06:27 /tmp/data/pg_time
bohemia:aoki (13)> uname -a
SunOS bohemia.cs.berkeley.edu 5.3 Generic sun4m sparc

i just unpacked the binary distribution (which uses gcc) and 
used that.  our solaris compiler license expired again so i 
can't check that.

a sparse log file would normally suggest a lot of aborts, but it
seems hard to believe that postgres could even manage to *parse*
8 * 134,000,000 queries overnight, so i have no idea what might
be causing what you're seeing.. all i can say is, try the binary
distribution (if you aren't already) and see what happens.
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776

==============================================================================
   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.
==============================================================================
