Re: [COMMITTERS] pgsql: Add lock matrix to documentation. - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Add lock matrix to documentation.
Date
Msg-id 45CC857F.70104@dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Add lock matrix to documentation.  (Oleg Bartunov <oleg@sai.msu.su>)
List 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 by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: [COMMITTERS] pgsql: Add lock matrix to documentation.
Next
From: Martijn van Oosterhout
Date:
Subject: Re: [PATCHES] How can I use 2GB of shared buffers on Windows?