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
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
