Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Commit1ba8410

Browse files
committed
doc: Improve description of index vacuuming with GUCs
Index vacuums may happen multiple times depending on the number of deadtuples stored, as of maintenance_work_mem for a manual VACUUM. Forautovacuum, this is controlled by autovacuum_work_mem instead, if set.The documentation mentioned the former, but not the latter in thecontext of autovacuum.Reported-by: Nikolai BerkoffAuthor: Laurenz Albe, Euler TaveiraDiscussion:https://postgr.es/m/161545365522.10134.12195402324485546870@wrigleys.postgresql.orgBackpatch-through: 9.6
1 parent1ab70b1 commit1ba8410

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎doc/src/sgml/monitoring.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6147,8 +6147,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
61476147
<command>VACUUM</command> is currently vacuuming the indexes. If a table has
61486148
any indexes, this will happen at least once per vacuum, after the heap
61496149
has been completely scanned. It may happen multiple times per vacuum
6150-
if <xref linkend="guc-maintenance-work-mem"/> is insufficient to
6151-
store the number of dead tuples found.
6150+
if <xref linkend="guc-maintenance-work-mem"/> (or, in the case of autovacuum,
6151+
<xref linkend="guc-autovacuum-work-mem"/> if set) is insufficient to store
6152+
the number of dead tuples found.
61526153
</entry>
61536154
</row>
61546155
<row>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp