Return-Path: owner-postman
Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id OAA25545 for postgres-dist; Fri, 28 Jan 1994 14:34:03 -0800
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199401282234.OAA25545@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from liblas.byu.edu (liblas.byu.edu [128.187.11.118]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id OAA25536 for <postgres@nobozo.CS.Berkeley.EDU>; Fri, 28 Jan 1994 14:34:00 -0800
Received: by liblas.byu.edu; id AA00690; Fri, 28 Jan 1994 15:36:16 -0700
From: Brian Holman <bkh@liblas.byu.edu>
Message-Id: <9401282236.AA00690@liblas.byu.edu>
Subject: Postgres v4.2? OSF/1 Port?
To: postgres@postgres.Berkeley.EDU
Date: Fri, 28 Jan 1994 15:36:15 +119303928 (MST)
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text
Content-Length: 1737      
Resent-To: postgres-dist@postgres.Berkeley.EDU
Resent-Date: Fri, 28 Jan 94 14:34:03 -0800
Resent-XMts: smtp

Quoted from Mike Stonebraker <mike@postgres.Berkeley.EDU>

>We both agreed that code freeze will be 2/1.  She will either have her "new"
>implementation robust and as functional as the old one by that date, or she
>will fall back to the "old" implementation.

>As such, we can move ahead with a schedule based on a firm 2/1 code freeze.

Does this mean that the Postgres V4.2 is near completion?  Is there a
estimated release date yet?  Is the DEC Alpha OSF/1 port sufficently stable
to be included in the next release?

Another question:  I'm running Postgres V4.1 on a DECStation 5000 running
Ultrix.  I have some non-critical production databases running on it that
log statistical information.  In other words, there are alot of very brief
transactions being send to the postmaster.

About once a day the postmaster dies and has to be restarted.  I wrote the
following script to eliminate the need for a human to restart the
postmaster.  It gets run as "pgloop.csh &".

-------pgloop.csh--------
#!/bin/csh
while 1 == 1
	postmaster
	mail -s "Backend went down" bkh@liblas </dev/null
	sleep 30
end
-------------------------

Why is the back end keep going down?  Is it the number of "postgres"
processes running at a time?  Does shared memory just get screwed up every
once in a while or what?  Any ideas would be appreciated.

-- 
+--------------------------+-------------------------------------+
| BRIAN K. HOLMAN          | E-Mail:        brian_holman@byu.edu |
| Programmer/Analyst       | Mail:    2330 HBLL, Provo, UT 84602 |
| Library Automations      | Phone:               (801) 378-8162 |
| Brigham Young University | Fax:                 (801) 378-3221 |
+--------------------------+-------------------------------------+
