Return-Path: laurie@basser.cs.su.oz.AU
Received: from metro.ucc.su.OZ.AU by postgres.Berkeley.EDU (5.61/1.29)
	id AA07342; Wed, 24 Jul 91 03:47:03 -0700
Received: by metro.ucc.su.OZ.AU (5.61/1.34)
	id AA23913; Wed, 24 Jul 1991 20:47:16 +1000
Message-Id: <9107241047.AA23913@metro.ucc.su.OZ.AU>
Date: Wed, 24 Jul 1991 20:39:19 +1000
From: laurie@cs.su.oz.au ("Lawrence F.M. Lo")
Subject: Re: SunOS Release 4.1.1
To: pg_adm@postgres.Berkeley.EDU


This might not be SunOS 's problem, probably it is due to POSTGRES
version 2.1 itself, i have a similar problem before and i m using 
SunOS 4.1 and POSTGRES version 2.3. the following are the mesg. given
by the postgres research gp in Berkely.

version 2.1 of postgres has known reliability problems; the behavior you
describe is one symptom.  what's happening is that shared locking in 2.1
is broken, and processes are sleeping forever, trying to acquire locks that
other processes never release.  for the time being, killing and restarting
the postmaster is the only workaround.  version 3.0 should be out in a
few weeks, and will fix the problems you're seeing.

hope this help.
If you know some more about the workaround solution. Please let me know.

Lawrence Lo. 
Sydney Uni.

