summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian2014-09-10 21:13:04 +0000
committerBruce Momjian2014-09-10 21:13:04 +0000
commit36ad1a87a368d837d5c2260b2fd2ff83e976425a (patch)
treeb951f5f04b2f8f46f3d5947e092590b7f248d07d /doc/src
parent84aa8ba128a08e6fdebb2497c7a79ebf18093e12 (diff)
Implement mxid_age() to compute multi-xid age
Report by Josh Berkus
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/maintenance.sgml7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index cf174f07157..d692308cf49 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -640,7 +640,12 @@ HINT: Stop the postmaster and vacuum that database in single-user mode.
possible multixact ID still appearing in any tuple of that table.
If this value is older than
<xref linkend="guc-vacuum-multixact-freeze-table-age">, a whole-table
- scan is forced. Whole-table <command>VACUUM</> scans, regardless of
+ scan is forced. <function>mxid_age()</> can be used on
+ <structname>pg_class</>.<structfield>relminmxid</> to find its age.
+ </para>
+
+ <para>
+ Whole-table <command>VACUUM</> scans, regardless of
what causes them, enable advancing the value for that table.
Eventually, as all tables in all databases are scanned and their
oldest multixact values are advanced, on-disk storage for older