1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
|
'\" t
.\" Title: ANALYZE
.\" Author: The PostgreSQL Global Development Group
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
.\" Date: 2023
.\" Manual: PostgreSQL 15.5 Documentation
.\" Source: PostgreSQL 15.5
.\" Language: English
.\"
.TH "ANALYZE" "7" "2023" "PostgreSQL 15.5" "PostgreSQL 15.5 Documentation"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
ANALYZE \- collect statistics about a database
.SH "SYNOPSIS"
.sp
.nf
ANALYZE [ ( \fIoption\fR [, \&.\&.\&.] ) ] [ \fItable_and_columns\fR [, \&.\&.\&.] ]
ANALYZE [ VERBOSE ] [ \fItable_and_columns\fR [, \&.\&.\&.] ]
where \fIoption\fR can be one of:
VERBOSE [ \fIboolean\fR ]
SKIP_LOCKED [ \fIboolean\fR ]
and \fItable_and_columns\fR is:
\fItable_name\fR [ ( \fIcolumn_name\fR [, \&.\&.\&.] ) ]
.fi
.SH "DESCRIPTION"
.PP
\fBANALYZE\fR
collects statistics about the contents of tables in the database, and stores the results in the
pg_statistic
system catalog\&. Subsequently, the query planner uses these statistics to help determine the most efficient execution plans for queries\&.
.PP
Without a
\fItable_and_columns\fR
list,
\fBANALYZE\fR
processes every table and materialized view in the current database that the current user has permission to analyze\&. With a list,
\fBANALYZE\fR
processes only those table(s)\&. 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\&.
.PP
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\&.
.SH "PARAMETERS"
.PP
VERBOSE
.RS 4
Enables display of progress messages\&.
.RE
.PP
SKIP_LOCKED
.RS 4
Specifies that
\fBANALYZE\fR
should not wait for any conflicting locks to be released when beginning work on a relation: if a relation cannot be locked immediately without waiting, the relation is skipped\&. Note that even with this option,
\fBANALYZE\fR
may still block when opening the relation\*(Aqs indexes or when acquiring sample rows from partitions, table inheritance children, and some types of foreign tables\&. Also, while
\fBANALYZE\fR
ordinarily processes all partitions of specified partitioned tables, this option will cause
\fBANALYZE\fR
to skip all partitions if there is a conflicting lock on the partitioned table\&.
.RE
.PP
\fIboolean\fR
.RS 4
Specifies whether the selected option should be turned on or off\&. You can write
TRUE,
ON, or
1
to enable the option, and
FALSE,
OFF, or
0
to disable it\&. The
\fIboolean\fR
value can also be omitted, in which case
TRUE
is assumed\&.
.RE
.PP
\fItable_name\fR
.RS 4
The name (possibly schema\-qualified) of a specific table to analyze\&. If omitted, all regular tables, partitioned tables, and materialized views in the current database are analyzed (but not foreign tables)\&. If the specified table is a partitioned table, both the inheritance statistics of the partitioned table as a whole and statistics of the individual partitions are updated\&.
.RE
.PP
\fIcolumn_name\fR
.RS 4
The name of a specific column to analyze\&. Defaults to all columns\&.
.RE
.SH "OUTPUTS"
.PP
When
VERBOSE
is specified,
\fBANALYZE\fR
emits progress messages to indicate which table is currently being processed\&. Various statistics about the tables are printed as well\&.
.SH "NOTES"
.PP
To analyze a table, one must ordinarily be the table\*(Aqs owner or a superuser\&. However, database owners are allowed to analyze all tables in their databases, except shared catalogs\&. (The restriction for shared catalogs means that a true database\-wide
\fBANALYZE\fR
can only be performed by a superuser\&.)
\fBANALYZE\fR
will skip over any tables that the calling user does not have permission to analyze\&.
.PP
Foreign tables are analyzed only when explicitly selected\&. Not all foreign data wrappers support
\fBANALYZE\fR\&. If the table\*(Aqs wrapper does not support
\fBANALYZE\fR, the command prints a warning and does nothing\&.
.PP
In the default
PostgreSQL
configuration, the autovacuum daemon (see
Section\ \&25.1.6) takes care of automatic analyzing of tables when they are first loaded with data, and as they change throughout regular operation\&. When autovacuum is disabled, it is a good idea to run
\fBANALYZE\fR
periodically, or just after making major changes in the contents of a table\&. Accurate statistics will help the planner to choose the most appropriate query plan, and thereby improve the speed of query processing\&. A common strategy for read\-mostly databases is to run
\fBVACUUM\fR
and
\fBANALYZE\fR
once a day during a low\-usage time of day\&. (This will not be sufficient if there is heavy update activity\&.)
.PP
\fBANALYZE\fR
requires only a read lock on the target table, so it can run in parallel with other activity on the table\&.
.PP
The statistics collected by
\fBANALYZE\fR
usually include a list of some of the most common values in each column and a histogram showing the approximate data distribution in each column\&. One or both of these can be omitted if
\fBANALYZE\fR
deems them uninteresting (for example, in a unique\-key column, there are no common values) or if the column data type does not support the appropriate operators\&. There is more information about the statistics in
Chapter\ \&25\&.
.PP
For large tables,
\fBANALYZE\fR
takes a random sample of the table contents, rather than examining every row\&. This allows even very large tables to be analyzed in a small amount of time\&. Note, however, that the statistics are only approximate, and will change slightly each time
\fBANALYZE\fR
is run, even if the actual table contents did not change\&. This might result in small changes in the planner\*(Aqs estimated costs shown by
\fBEXPLAIN\fR\&. In rare situations, this non\-determinism will cause the planner\*(Aqs choices of query plans to change after
\fBANALYZE\fR
is run\&. To avoid this, raise the amount of statistics collected by
\fBANALYZE\fR, as described below\&.
.PP
The extent of analysis can be controlled by adjusting the
default_statistics_target
configuration variable, or on a column\-by\-column basis by setting the per\-column statistics target with
\fBALTER TABLE \&.\&.\&. ALTER COLUMN \&.\&.\&. SET STATISTICS\fR\&. The target value sets the maximum number of entries in the most\-common\-value list and the maximum number of bins in the histogram\&. The default target value is 100, but this can be adjusted up or down to trade off accuracy of planner estimates against the time taken for
\fBANALYZE\fR
and the amount of space occupied in
pg_statistic\&. In particular, setting the statistics target to zero disables collection of statistics for that column\&. It might be useful to do that for columns that are never used as part of the
WHERE,
GROUP BY, or
ORDER BY
clauses of queries, since the planner will have no use for statistics on such columns\&.
.PP
The largest statistics target among the columns being analyzed determines the number of table rows sampled to prepare the statistics\&. Increasing the target causes a proportional increase in the time and space needed to do
\fBANALYZE\fR\&.
.PP
One of the values estimated by
\fBANALYZE\fR
is the number of distinct values that appear in each column\&. Because only a subset of the rows are examined, this estimate can sometimes be quite inaccurate, even with the largest possible statistics target\&. If this inaccuracy leads to bad query plans, a more accurate value can be determined manually and then installed with
\fBALTER TABLE \&.\&.\&. ALTER COLUMN \&.\&.\&. SET (n_distinct = \&.\&.\&.)\fR\&.
.PP
If the table being analyzed has inheritance children,
\fBANALYZE\fR
gathers two sets of statistics: one on the rows of the parent table only, and a second including rows of both the parent table and all of its children\&. This second set of statistics is needed when planning queries that process the inheritance tree as a whole\&. The child tables themselves are not individually analyzed in this case\&. The autovacuum daemon, however, will only consider inserts or updates on the parent table itself when deciding whether to trigger an automatic analyze for that table\&. If that table is rarely inserted into or updated, the inheritance statistics will not be up to date unless you run
\fBANALYZE\fR
manually\&.
.PP
For partitioned tables,
\fBANALYZE\fR
gathers statistics by sampling rows from all partitions; in addition, it will recurse into each partition and update its statistics\&. Each leaf partition is analyzed only once, even with multi\-level partitioning\&. No statistics are collected for only the parent table (without data from its partitions), because with partitioning it\*(Aqs guaranteed to be empty\&.
.PP
The autovacuum daemon does not process partitioned tables, nor does it process inheritance parents if only the children are ever modified\&. It is usually necessary to periodically run a manual
\fBANALYZE\fR
to keep the statistics of the table hierarchy up to date\&.
.PP
If any child tables or partitions are foreign tables whose foreign data wrappers do not support
\fBANALYZE\fR, those tables are ignored while gathering inheritance statistics\&.
.PP
If the table being analyzed is completely empty,
\fBANALYZE\fR
will not record new statistics for that table\&. Any existing statistics will be retained\&.
.PP
Each backend running
\fBANALYZE\fR
will report its progress in the
pg_stat_progress_analyze
view\&. See
Section\ \&28.4.1
for details\&.
.SH "COMPATIBILITY"
.PP
There is no
\fBANALYZE\fR
statement in the SQL standard\&.
.SH "SEE ALSO"
\fBVACUUM\fR(7), \fBvacuumdb\fR(1), Section\ \&20.4.4, Section\ \&25.1.6, Section\ \&28.4.1
|
