Merlin Moncure wrote:
> > > 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", a
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. Al
OK, I have updated "Conflicting lock modes" to show as conflicts, added
"Current/Requested" headings, add linked to the table from text. Here
is the updated version:
http://momjian.us/main/writings/pgsql/sgml/explicit-locking.html#TABLE-LOCK-COMPATIBILITY
--
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 whe
On 2/9/07, 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,
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.
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
