From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_class.relminmxid and pg_database.datminmxid |
Date: | 2015-06-04 03:35:10 |
Message-ID: | CAHGQGwEG7Uiq5s4sxN-HLvunYYy9WvmLAPszeHiXFs2fhS1QwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Jun 4, 2015 at 3:22 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Seltenreich | 2015-06-05 08:00:34 | [PATCH] doc: Fix typo in logicaldecoding.sgml. |
Previous Message | Alvaro Herrera | 2015-06-03 18:22:36 | Re: pg_class.relminmxid and pg_database.datminmxid |