Re: Minor improvement in lock.sgml

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Minor improvement in lock.sgml
Date: 2014-09-19 17:13:16
Message-ID: CA+TgmoZmp4kAYriU=5sVct6ttiSMuAV4j3sHt+heJ=Q7oX09uQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 16, 2014 at 7:20 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Here is a patch to a bit improve the reference page for the LOCK
> command. I think it'd be better for the isolation level to be in
> capitals and wrapped in the <literal> tags.

It's done that way elsewhere in the same page, so committed.

Overall, there is some ambiguity about this. Most places follow your
proposed style if <literal>READ COMMITTED</literal>,
<literal>REPEATABLE READ</literal>, and
<literal>SERIALIZABLE</literal>, but mvcc.sgml, which discusses
isolation levels extensively, just writes them as Read Committed,
Repeatable Read, and Serializable.

I'm not sure whether more consistency overall would be a good thing -
there are some things to recommend the current mix of styles - but
mixing styles within a page doesn't seem smart, so this much at least
seems uncontroversial.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2014-09-19 17:15:34 Re: Yet another abort-early plan disaster on 9.3
Previous Message Robert Haas 2014-09-19 16:59:39 Re: B-Tree support function number 3 (strxfrm() optimization)