Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 13e2607

Browse filesBrowse files
committed
Update documentation to mention that autovacuum also does analyze so we
don't need to recommend nightly analyzes anymore unless autovacuum is off.
1 parent fc79628 commit 13e2607
Copy full SHA for 13e2607

File tree

Expand file treeCollapse file tree

1 file changed

+14
-7
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+14
-7
lines changed

‎doc/src/sgml/maintenance.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/maintenance.sgml
+14-7Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.80 2007/09/14 02:43:18 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.81 2007/09/14 13:43:03 momjian Exp $ -->
22

33
<chapter id="maintenance">
44
<title>Routine Database Maintenance Tasks</title>
@@ -262,12 +262,19 @@
262262
</tip>
263263

264264
<para>
265-
Recommended practice for most sites is to schedule a database-wide
266-
<command>ANALYZE</> once a day at a low-usage time of day; this can
267-
usefully be combined with a nightly <command>VACUUM</>. However,
268-
sites with relatively slowly changing table statistics might find that
269-
this is overkill, and that less-frequent <command>ANALYZE</> runs
270-
are sufficient.
265+
Fortunately, autovacuum (<xref linkend="autovacuum">) monitors table
266+
activity and performs <command>ANALYZE</command>s when necessary. This
267+
eliminates the need for administrators to manually schedule
268+
<command>ANALYZE</command>.
269+
</para>
270+
271+
<para>
272+
For those not using autovacuum, one approach is to schedule a
273+
database-wide <command>ANALYZE</> once a day at a low-usage time of
274+
day; this can usefully be combined with a nightly <command>VACUUM</>.
275+
However, sites with relatively slowly changing table statistics might
276+
find that this is overkill, and that less-frequent <command>ANALYZE</>
277+
runs are sufficient.
271278
</para>
272279
</sect2>
273280

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.