Re: [COMMITTERS] pgsql: Add lock matrix to documentation.
От | Andrew Dunstan |
---|---|
Тема | Re: [COMMITTERS] pgsql: Add lock matrix to documentation. |
Дата | |
Msg-id | 45CC857F.70104@dunslane.net обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Add lock matrix to documentation. (Oleg Bartunov <oleg@sai.msu.su>) |
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: