Re: pgsql: Add lock matrix to documentation. - Mailing list pgsql-committers

From Oleg Bartunov
Subject Re: pgsql: Add lock matrix to documentation.
Date
Msg-id Pine.LNX.4.64.0702091432000.400@sn.sai.msu.ru
Whole thread Raw
In response to Re: pgsql: Add lock matrix to documentation.  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pgsql: Add lock matrix to documentation.  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: pgsql: Add lock matrix to documentation.  (Andrew Dunstan <andrew@dunslane.net>)
Re: [HACKERS] pgsql: Add lock matrix to documentation.  (Bruce Momjian <bruce@momjian.us>)
List pgsql-committers
On Fri, 9 Feb 2007, Peter Eisentraut wrote:

> Am Donnerstag, 8. Februar 2007 16:32 schrieb Bruce Momjian:
>> Log Message:
>> -----------
>> Add lock matrix to documentation.
>
> This needs some revisions.  The table needs to be mentioned somewhere in the
> text, so the reader knows when or why to refer to it.  Also, the cryptic
> abbreviations need to be expanded or explained.  And then the concept of
> lock "compatibility", as the table puts it, is not used anywhere else in the
> documentation.  The table should be put in terms of conflicts instead.
>

Another version with expanded abbreviations is
http://mira.sai.msu.su/~megera/pgsql/lockmatrix/c2.html, if remove
UPDATE EXCLUSIVE.

While compatibility matrix is a commonly accepted termin, I agree, that
using conficts would be better in context of our docs.

     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgsql: Add lock matrix to documentation.
Next
From: Heikki Linnakangas
Date:
Subject: Re: plpsm - plpgpsm: prepare for phantom cid