ANALYZE [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
-ANALYZE [ VERBOSE ] [ table_and_columns [, ...] ]
where option can be one of:
It is further possible to give a list of column names for a table,
in which case only the statistics for those columns are collected.
-
- When the option list is surrounded by parentheses, the options can be
- written in any order. The parenthesized syntax was added in
-
PostgreSQL 11; the unparenthesized syntax
- is deprecated.
-
There is no ANALYZE statement in the SQL standard.
+
+ The following syntax was used before
PostgreSQL
+ version 11 and is still supported:
+
+ANALYZE [ VERBOSE ] [ table_and_columns [, ...] ]
+
+
CLUSTER [ ( option [, ...] ) ] [ table_name [ USING index_name ] ]
-CLUSTER [ VERBOSE ] [ table_name [ USING index_name ] ]
where option can be one of:
- The syntax
+ The following syntax was used before
PostgreSQL
+ 17 and is still supported:
+
+CLUSTER [ VERBOSE ] [ table_name [ USING index_name ] ]
+
+
+
+ The following syntax was used before
PostgreSQL
+ 8.3 and is still supported:
CLUSTER index_name ON table_name
- is also supported for compatibility with pre-8.3
PostgreSQL
- versions.
EXPLAIN [ ( option [, ...] ) ] statement
-EXPLAIN [ ANALYZE ] [ VERBOSE ] statement
where option can be one of:
-
- Only the ANALYZE and VERBOSE options
- can be specified, and only in that order, without surrounding the option
- list in parentheses. Prior to
PostgreSQL 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.
-
There is no EXPLAIN statement defined in the SQL standard.
+
+ The following syntax was used before
PostgreSQL
+ version 9.0 and is still supported:
+
+EXPLAIN [ ANALYZE ] [ VERBOSE ] statement
+
+ Note that in this syntax, the options must be specified in exactly the order
+ shown.
+
VACUUM [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
-VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ table_and_columns [, ...] ]
where option can be one of:
much slower and requires an ACCESS EXCLUSIVE lock on
each table while it is being processed.
-
- 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.
- The parenthesized syntax was added in
-
PostgreSQL 9.0; the unparenthesized
- syntax is deprecated.
-
There is no VACUUM statement in the SQL standard.
+
+ The following syntax was used before
PostgreSQL
+ version 9.0 and is still supported:
+
+VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ table_and_columns [, ...] ]
+
+ Note that in this syntax, the options must be specified in exactly the order
+ shown.
+