Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA21239; Tue, 4 Aug 92 23:39:27 -0700
Date: Tue, 4 Aug 92 23:39:27 -0700
Message-Id: <9208050639.AA21239@postgres.Berkeley.EDU>
From: bunting@pangaea.dme.nt.gov.au (Chris Bunting 95334)
Subject: Multi User Bug Fix
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Cc: bug-postgres@postgres.Berkeley.EDU

Dear Mr postgres.
You may not recall my recent mail on a monstering bug that mangles a class when more than one user is involved with appends, deletes and/or replaces.

This is causing us much heartache and headache.
Passing a postgres token around 200 users who thought they were part of a multiuser net is hard for us to explain.
In fact they think we are a bunch of wankers. They don't appear to appreciate the lengths we have gone to to log and reconstruct classes and instances at the drop of a hat.
Please can you help us, or even give us a hint of where to start looking.