From: Robert Haas <rhaas@postgresql.org>
Date: Tue, 14 Jan 2014 19:48:57 +0000 (-0500)
Subject: Mention that VACUUM FREEZE also effectively zeroes the table freeze age.
X-Git-Tag: REL9_4_BETA1~689
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b682709451b17333b038af9f2907c523754dacce;p=postgresql

Mention that VACUUM FREEZE also effectively zeroes the table freeze age.

Maciek Sakrejda, reviewed by Amit Kapila
---

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 1e984734d9..23c3ca89c7 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -101,7 +101,8 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
       Selects aggressive <quote>freezing</quote> of tuples.
       Specifying <literal>FREEZE</literal> is equivalent to performing
       <command>VACUUM</command> with the
-      <xref linkend="guc-vacuum-freeze-min-age"> parameter
+      <xref linkend="guc-vacuum-freeze-min-age"> and
+      <xref linkend="guc-vacuum-freeze-table-age"> parameters
       set to zero.  Aggressive freezing is always performed when the
       table is rewritten, so this option is redundant when <literal>FULL</>
       is specified.