pgsql: Add lock matrix to documentation.
Log Message:
-----------
Add lock matrix to documentation.
Teodor Sigaev
Modified Files:
--------------
pgsql/doc/src/sgml:
mvcc.sgml (r2.66 -> r2.67)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/mvcc.sgml.diff?r1=2.66&r2=2.67)
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.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
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
On 2/9/07, Oleg Bartunov <oleg@sai.msu.su> wrote:
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.
How about changing 'current lock mode' to 'opposing lock mode'?
'current' kind of suggests that you are escalating your own lock.
merlin
Oleg Bartunov wrote:
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.
If UE is moved 2 or 3 places down/right, the matrix will be closer to
triangular.
It would look better with non-conflicts being blank (or in HTML)
rather than 'O', I think - the conflicts will stand out more.
cheers
andrew
OK, I have updated "Conflicting lock modes" to show as conflicts, added
"Current/Requested" headings, add linked to the table from text. Here
is the updated version:
http://momjian.us/main/writings/pgsql/sgml/explicit-locking.html#TABLE-LOCK-COMPATIBILITY
---------------------------------------------------------------------------
Oleg Bartunov wrote:
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---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Merlin Moncure wrote:
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.How about changing 'current lock mode' to 'opposing lock mode'?
'current' kind of suggests that you are escalating your own lock.
Not sure how you can say requested and opposing --- they seems odd
together. I am still open to new working though:
http://momjian.us/main/writings/pgsql/sgml/explicit-locking.html#TABLE-LOCK-COMPATIBILITY
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
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.
Done.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +