Re: Minor improvement in lock.sgml - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Minor improvement in lock.sgml
Date
Msg-id CA+TgmoZmp4kAYriU=5sVct6ttiSMuAV4j3sHt+heJ=Q7oX09uQ@mail.gmail.com
Whole thread Raw
In response to Minor improvement in lock.sgml  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: Minor improvement in lock.sgml
List pgsql-hackers
On Tue, Sep 16, 2014 at 7:20 AM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)
Next
From: Robert Haas
Date:
Subject: Re: Support for N synchronous standby servers