MIME-Version: 1.0
In-Reply-To: <20150603182236.GC133018@postgresql.org>
References: 
 <CAHGQGwEWkRSCGVYGwVYAWTJeMHEiVYKRrhYL_nC++F+95r4M6A@mail.gmail.com>
 <20150603182236.GC133018@postgresql.org>
Date: Thu, 4 Jun 2015 12:35:10 +0900
Message-ID: 
 <CAHGQGwEG7Uiq5s4sxN-HLvunYYy9WvmLAPszeHiXFs2fhS1QwA@mail.gmail.com>
Subject: Re: pg_class.relminmxid and pg_database.datminmxid
From: Fujii Masao <masao.fujii@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Thu, Jun 4, 2015 at 3:22 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Fujii Masao wrote:
>> Hi,
>>
>> The descriptions of pg_class.relminmxid and pg_database.datminmxid
>> have some minor problems in the doc. Seems the attached patch needs
>> to be applied.
>
> Looks reasonable.  I'm not sure about the term "multitransaction"
> anymore; we use "multixact" elsewhere (notably in the section that
> explains freezing, in the maintenance chapter).

Yes, we seem to have priority use of "multixact". OTOH, I found that
"multitransaction" is also used elsewhere, for example, in storage.sgml
(description of pg_multixact directory), pg_resetxlog.sgml and pgrowlocks.sgml.
Maybe it's better to use "multixact" even there...

Anyway I will push the fix with the term "multixact".

Regards,

-- 
Fujii Masao


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs