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
*** a/doc/src/sgml/catalogs.sgml
--- b/doc/src/sgml/catalogs.sgml
***************
*** 2018,2025 ****
All multitransaction IDs before this one have been replaced by a
transaction ID in this table. This is used to track
whether the table needs to be vacuumed in order to prevent multitransaction ID
! ID wraparound or to allow <literal>pg_clog</> to be shrunk. Zero
! (<symbol>InvalidTransactionId</symbol>) if the relation is not a table.
</entry>
</row>
--- 2018,2025 ----
All multitransaction IDs before this one have been replaced by a
transaction ID in this table. This is used to track
whether the table needs to be vacuumed in order to prevent multitransaction ID
! wraparound or to allow <literal>pg_multixact</> to be shrunk. Zero
! (<symbol>InvalidMultiXactId</symbol>) if the relation is not a table.
</entry>
</row>
***************
*** 2686,2692 ****
All multitransaction IDs before this one have been replaced with a
transaction ID in this database. This is used to
track whether the database needs to be vacuumed in order to prevent
! transaction ID wraparound or to allow <literal>pg_clog</> to be shrunk.
It is the minimum of the per-table
<structname>pg_class</>.<structfield>relminmxid</> values.
</entry>
--- 2686,2692 ----
All multitransaction IDs before this one have been replaced with a
transaction ID in this database. This is used to
track whether the database needs to be vacuumed in order to prevent
! multitransaction ID wraparound or to allow <literal>pg_multixact</> to be shrunk.
It is the minimum of the per-table
<structname>pg_class</>.<structfield>relminmxid</> values.
</entry>
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
