Re: pgsql: Add lock matrix to documentation.

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql: Add lock matrix to documentation.
Date: 2007-02-09 10:39:33
Message-ID: 200702091139.34775.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message User Okbob 2007-02-09 11:05:56 plpsm - plpgpsm: prepare for phantom cid
Previous Message User Okbob 2007-02-09 09:04:33 plpsm - plpgpsm: recompile option supported It allows recompile every

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-02-09 11:20:03 Re: [PATCHES] [pgsql-patches] Phantom Command IDs,updated patch
Previous Message Takayuki Tsunakawa 2007-02-09 10:31:33 Re: [PATCHES] How can I use 2GB of shared buffers on Windows?