Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA00649; Thu, 12 Mar 92 10:37:36 -0800
Message-Id: <9203121837.AA00649@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: 2-phase locks and deadlocks
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Thu, 12 Mar 92 07:56:54 PST."
             <9203121556.AA28668@postgres.Berkeley.EDU> 
Date: Thu, 12 Mar 92 10:37:27 PST

you write:

> does postgres really deal differently with read-only
> transactions? i mean, does it allow any number of concurrent
> transactions to access classes for retrieval-only
> operations without locking them exclusively?

read locks do not conflict with each other.  So there can be arbitrarily
many transactions setting read locks on a single relation at the same
time.


Jeff Meredith
mer@postgres.berkeley.edu