Re: docs: additional subsection for page-level locks in explicit-locking section

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Michael Banck <michael(dot)banck(at)credativ(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: docs: additional subsection for page-level locks in explicit-locking section
Date: 2014-07-03 15:51:36
Message-ID: 1404402696.86163.YahooMailNeo@web122303.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> This seems to make sense. Barring objection, I will commit this
> only in HEAD.

I'm inclined to think this is a slight improvement, just for the
sake of consistency with peer level information.  You probably
already noticed, but the patch as submitted neglects to close the
prior sect2 block before opening the new one.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Joseph Krogh 2014-07-03 15:54:05 Re: Setting PG-version without recompiling
Previous Message Tom Lane 2014-07-03 14:37:38 Re: "RETURNING PRIMARY KEY" syntax extension