agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Brian Holman <[email protected]>
To: [email protected]
Subject: Postgres v4.2? OSF/1 Port?
Date: Fri, 28 Jan 1994 15:36:15 +0000 (MST)
Message-ID: <[email protected]> (raw)
Quoted from Mike Stonebraker <[email protected]>
>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: [email protected] |
| Programmer/Analyst | Mail: 2330 HBLL, Provo, UT 84602 |
| Library Automations | Phone: (801) 378-8162 |
| Brigham Young University | Fax: (801) 378-3221 |
+--------------------------+-------------------------------------+
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: [email protected]
Cc: [email protected]
Subject: Re: Postgres v4.2? OSF/1 Port?
In-Reply-To: <[email protected]>
* 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