Обсуждение: pg_class.relminmxid and pg_database.datminmxid

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.

Regards,

--
Fujii Masao

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).

Make sure to backpatch to 9.3 ...




--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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