Kevin Grittner wrote:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>
> >> shouldn't we be getting support for the new syntax added, so
> >> there can be a release or two supporting both?
> >
> > You mean like 9.0?
>
> Yeah, just like that.
>
> If we're going to be supporting that long term, we should probably
> change the note about FREEZE being deprecated, though.
>
> So, still +1 on removing the wording about FREEZE being deprecated,
> but instead we should mention what actually *is* deprecated (the
> omission of the parentheses).
Done with the attached, applied patch.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index dee1cc3..5b5b161 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -70,9 +70,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
When the option list is surrounded by parentheses, the options can be
written in any order. Without parentheses, options must be specified
in exactly the order shown above.
- Prior to <productname>PostgreSQL</productname> 9.0, the unparenthesized
- syntax was the only one supported. It is expected that all new options
- will be supported only in the parenthesized syntax.
+ The unparenthesized syntax was added in
+ <productname>PostgreSQL</productname> 9.0; the unparenthesized
+ syntax is deprecated.
</para>
</refsect1>
@@ -102,8 +102,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
Specifying <literal>FREEZE</literal> is equivalent to performing
<command>VACUUM</command> with the
<xref linkend="guc-vacuum-freeze-min-age"> parameter
- set to zero. The <literal>FREEZE</literal> option is deprecated and
- will be removed in a future release; set the parameter instead.
+ set to zero.
</para>
</listitem>
</varlistentry>
