public inbox for [email protected]help / color / mirror / Atom feed
pg_class.relminmxid and pg_database.datminmxid 3+ messages / 2 participants [nested] [flat]
* pg_class.relminmxid and pg_database.datminmxid @ 2015-06-03 15:59 Fujii Masao <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Fujii Masao @ 2015-06-03 15:59 UTC (permalink / raw) To: pgsql-docs 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 -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs Attachments: [text/x-diff] multixact_doc_v1.patch (1.8K, 2-multixact_doc_v1.patch) download | inline diff: *** 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> ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_class.relminmxid and pg_database.datminmxid @ 2015-06-03 18:22 Alvaro Herrera <[email protected]> parent: Fujii Masao <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Alvaro Herrera @ 2015-06-03 18:22 UTC (permalink / raw) To: Fujii Masao <[email protected]>; +Cc: pgsql-docs 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 -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_class.relminmxid and pg_database.datminmxid @ 2015-06-04 03:35 Fujii Masao <[email protected]> parent: Alvaro Herrera <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Fujii Masao @ 2015-06-04 03:35 UTC (permalink / raw) To: Alvaro Herrera <[email protected]>; +Cc: pgsql-docs On Thu, Jun 4, 2015 at 3:22 AM, Alvaro Herrera <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2015-06-04 03:35 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2015-06-03 15:59 pg_class.relminmxid and pg_database.datminmxid Fujii Masao <[email protected]> 2015-06-03 18:22 ` Alvaro Herrera <[email protected]> 2015-06-04 03:35 ` Fujii Masao <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox