Re: pgsql: Add lock matrix to documentation.

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql: Add lock matrix to documentation.
Date: 2007-02-09 11:36:25
Message-ID: Pine.LNX.4.64.0702091432000.400@sn.sai.msu.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-02-09 12:19:35 Re: plpsm - plpgpsm: prepare for phantom cid
Previous Message User Okbob 2007-02-09 11:05:56 plpsm - plpgpsm: prepare for phantom cid

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2007-02-09 11:40:59 Re: Proposal: TABLE functions
Previous Message Greg Stark 2007-02-09 11:33:04 Re: Variable length varlena headers redux