agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Paul M. Aoki <[email protected]>
To: MARCIN JANUCHTA (P.445) <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: concurrency control structures in Postgres
Date: Mon, 25 Apr 94 19:37:29 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
"MARCIN JANUCHTA (P.445)" <[email protected]> writes:
> Does anybody have the documentation concerning the lock table
> structure and lock request/grant routines in Postgres code,
> as well as the internal representation of transactions?
> I hope that somebody (perhaps from the Postgres team) would be
> so kind to enlighten me (if it's not a kind of trade secret...).
if it were a trade secret, we wouldn't give away the source, eh? :-)
the very little i know about the lock manager i acquired from
walking around with a TAGS-file. unfortunately there isn't much
in terms of documentation. there is a file
src/backend/storage/lmgr/README
that was a first attempt by jeff meredith at explaining some concepts
but it was never finished. there are also some comments in the source
that explain a few things. i believe the gray paper to which they
refer is:
%A J. N. Gray
%A R. A. Lorie
%A G. R. Putzolu
%A I. L. Traiger
%T Granularity of Locks and Degrees of Consistency in a Shared Data Base
%B Modelling in Data Base Management Systems
\fI(PROC IFIP Working CONF on Modelling in Data Base Management Systems, Freudenstadt, Germany, JAN 1976)\fP
%I North-Holland
%C Amsterdam, the Netherlands
%D 1976
%P 365-394
%O (Reprinted in: M. Stonebraker, \fIReadings in Database Systems, 2nd Ed.\fP, Morgan Kauffman, San Mateo, CA, 1993.)
(note that the recent gray/reuter book on transaction processing systems
has an improved version of the same discussion.)
--
Paul M. Aoki | CS Div., Dept. of EECS, UCB | [email protected]
| Berkeley, CA 94720 | ...!uunet!ucbvax!aoki
===============================================================================
To add/remove yourself from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "[email protected]"
If this fails, send mail to "[email protected]" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
===============================================================================
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: concurrency control structures in Postgres
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox