Re: [HACKERS] pgsql: Add lock matrix to documentation.

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] pgsql: Add lock matrix to documentation.
Date: 2007-02-18 01:30:54
Message-ID: 200702180130.l1I1Use04967@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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.

Done.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-18 01:32:56 pgsql: Add: * Allow SQL-language functions to reference parameters by
Previous Message Bruce Momjian 2007-02-18 01:30:40 Re: [HACKERS] pgsql: Add lock matrix to documentation.

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-18 01:34:44 Re: TODO: Allow SQL functions to reference parameters by name
Previous Message Bruce Momjian 2007-02-18 01:30:40 Re: [HACKERS] pgsql: Add lock matrix to documentation.