Return-Path: mao
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA03531; Wed, 18 Nov 92 10:37:59 -0800
Message-Id: <9211181837.AA03531@postgres.Berkeley.EDU>
From: <mao@postgres.berkeley.edu>
Subject: Re: postmaster crash
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Tue, 17 Nov 92 22:04:46 PST.
             <9211180604.AA01487@postgres.Berkeley.EDU> 
Date: Wed, 18 Nov 92 10:08:40 PST

In message <9211180604.AA01487@postgres.Berkeley.EDU> you write:

> 1) the postmaster crashes at around every 20 mins.
> 2) if we run the postmaster at separate machine (machines), it generates a lo
  +t of error logs.
> Our question is how to set postgres to support 30 different machines reliably
  +.

can you be more specific about problems one and two?  you should start up
the postmaster with the -d flag to turn on debugging output.

to support 30 machines, you'll need (at least) to recompile postgres with
a much larger shared buffer pool than is the default.  you can change
NDBUFS in src/lib/H/tmp/miscadmin.h; this value should be ten times the
number of active connections you expect, for reasonable performance.

					mike