Delivery-Date: Thu, 14 Oct 93 06:36:13 PDT
Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9310141325.AA08558@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Date: Thu, 14 Oct 93 09:29:02 -0400
From: witr@rwwa.COM
Message-Id: <9310141329.AA27826@relay1.UU.NET>
To: uunet!postgres.Berkeley.EDU!postgres@uunet.UU.NET
Subject: Re: survey summary
Content-Type: text
Content-Length: 823
Resent-To: postgres-dist
Resent-Date: Thu, 14 Oct 93 06:25:43 PDT

> If you have used Postgres for 6+ months and several people have been
> using your databases please email me.

Assuming that this is referring to concurrent access, then I can claim
that 4.0.1 fails when several processes are accessing the same
table(class) (some writing and some reading), resulting in the tuples
mysteriously dissapearing.

I haven't tried this with 4.1 yet.

What would help is if someone could post a test program stressing this
area of postgres that we could all run, and post the results here...

Alternatively, if the Dear Developers know of something wrong or
something that can be fixed in 4.1, I would *love* to hear about it...

Thanks!

---
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA