Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9311011206.AA08193@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
To: postgres@postgres.Berkeley.EDU
Path: jh
From: jh@efd.lth.se (Joergen Haegg)
Newsgroups: lth.lists.postgres
Subject: begin/end, where do I find more info about them?
Date: 1 Nov 1993 12:06:40 GMT
Organization: Lund Institute of Technology, Sweden
Lines: 18
Distribution: world
Message-Id: <2b2u4g$3vr@nic.lth.se>
Nntp-Posting-Host: baal.efd.lth.se
Resent-To: postgres-dist
Resent-Date: Mon, 01 Nov 93 04:06:47 PST

How are begin and end suppose to work?

It seems as if postgres locks the class completely for all
except the process that made the first append or replace.
It is locked for all other processes until the first process
executes 'end'.

Should it not be possible to read all instances, but not to change
any instance that has changed but not committed?

Can anyone explain this?


-- 
Joergen Haegg				jh@efd.lth.se
System manager @ efd			Phone: international +46 46 107492
Lund Institute of Technology		Snailmail: DDG, Maildelivery 7, BOX 118
Fax: +46 46 104013			S-221 00 LUND, Sweden