Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02094; Tue, 14 Apr 92 11:45:43 -0700
Message-Id: <9204141845.AA02094@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Dropping Sun3 (was Re: Demo Problems)
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of "Mon, 13 Apr 92 12:45:19 EDT."
             <9204131645.AA18504@SANDCASTLE.COSC.BROCKU.CA> 
Date: Tue, 14 Apr 92 11:45:27 PDT

you write:
> I am currently running POSTGRES on a SUN 3/60 with SUNOS4.1

The "Cache Invalidate" error message that you reported is a common problem
on Sun3 under SunOs 4.1.  The problem for me is that I no longer have a Sun3
to even try to chase down the problem.

For primarily this reason we are dropping support of Sun3 systems.
(Another reason being that postgres development and Postgres usage on
a Sun3 can both be painfully slow.)

Usually these types of problems relate to passing structures (instead of
pointers) on the stack.  I have made some changes for the next release to
keep this practice to a minimum, but I don't know if it will help.  This
is really your only hope, unless you can move to a {SPARC,DEC}station...


Sorry,

Jeff Meredith
mer@postgres.berkeley.edu