Return-Path: postman 
Delivery-Date: Thu, 14 Oct 93 15:24:30 PDT
Return-Path: postman
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA12941; Thu, 14 Oct 93 15:15:27 -0700
Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9310142215.AA12941@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: jean@gso.SAIC.COM
Received: from gefion.gso.saic.com by postgres.Berkeley.EDU (5.61/1.29)
	id AA12933; Thu, 14 Oct 93 15:15:21 -0700
Received: from ratatosk (ratatosk.gso.saic.com) by gso.SAIC.COM (4.1/SMI-4.1)
	id AA16965; Thu, 14 Oct 93 15:18:58 PDT
Received: by ratatosk (4.1/SMI-4.1)
	id AA01052; Thu, 14 Oct 93 15:18:56 PDT
Date: Thu, 14 Oct 93 15:18:56 PDT
From: jean@gso.SAIC.COM (Jean Anderson)
Message-Id: <9310142218.AA01052@ratatosk>
To: postgres@postgres.Berkeley.EDU
Subject: Re: Concurrency and locking
Resent-To: postgres-dist
Resent-Date: Thu, 14 Oct 93 15:15:25 PDT

Regarding what I wrote:
> I was cleaning up an old version of a test program that passed an 8 
> concurrent user test last Spring on my SUN 4/110.  It gets shared memory
> errors on my Sparc today :-( But if anybody wants to take a crack at it,
> I put it down below.

I should have mentioned that it should be cracked at cautiously.  When it 
gets shared memory errors, it hoses all backends on my system.

 -jean