Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA15363; Wed, 6 May 92 05:15:06 -0700
Date: Wed, 6 May 92 05:15:06 -0700
From: ambdata@dpi.inpe.br (Banco de Dados Ambiental)
Subject: vacuum
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.berkeley.edu
Message-Id: <9205061002.AA03662@dpi.inpe.br>
X-Envelope-To: postgres@postgres.berkeley.edu

I think my last message sent yesterday claims for more details.

I have a database where indexes and rules are defined along with nearly 40 relat
   ions. This database is used by sometime more than 8 users through copies of t
   he same application running in different Sun's. At the beginning of the datab
   ase's life everything seems to run OK, but some relatively long time latter t
   he backend begins not to respond for some of the frontend processes. To solve
    this problem I use to vacuum the database and call ipcclean to clean up shar
   ed memories. I don't know if this is the best action to take, so I would be g
   rateful for any suggestions or advices about the issue.

Thanks.

JPedro  ambdata@dpi.inpe.br