Re: [COMMITTERS] pgsql: Add documentation for new in-core advisory

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add documentation for new in-core advisory
Date: 2006-09-21 12:22:08
Message-ID: 1158841328.2586.437.camel@holly
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, 2006-09-20 at 20:43 -0300, Tom Lane wrote:
> Log Message:
> -----------
> Add documentation for new in-core advisory lock functions. Merlin Moncure
>
> Modified Files:
> --------------
> pgsql/doc/src/sgml:
> func.sgml (r1.338 -> r1.339)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.338&r2=1.339)
> mvcc.sgml (r2.62 -> r2.63)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/mvcc.sgml.diff?r1=2.62&r2=2.63)
>

Could we/should we make mention that this feature was provided as "user
locks" in previous versions of PostgreSQL, even if that specific module
has now been moved.

The release notes don't mention that the advisory locks feature has been
added either.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Teodor Sigaev 2006-09-21 15:03:53 pgsql: Fix table's caption
Previous Message Michael Meskes 2006-09-21 09:10:28 pgsql: Updated several parts in particular variable handling.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-21 13:52:36 Re: Phantom Command ID
Previous Message Heikki Linnakangas 2006-09-21 11:00:56 Re: Phantom Command ID