| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | nikolai(dot)berkoff(at)pm(dot)me |
| Subject: | Missing mention of autovacuum_work_mem |
| Date: | 2021-03-11 09:07:35 |
| Message-ID: | 161545365522.10134.12195402324485546870@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/progress-reporting.html
Description:
The "vacuuming indexes" documentation has:
"If a table has any indexes, this will happen at least once per vacuum,
after the heap has been completely scanned. It may happen multiple times per
vacuum if maintenance_work_mem is insufficient to store the number of dead
tuples found."
should be something like
"If a table has any indexes, this will happen at least once per vacuum,
after the heap has been completely scanned. It may happen multiple times per
vacuum if the maximum memory is insufficient to store the number of dead
tuples found. The maximum memory is set via the maintenance_work_mem unless
it is an autovacuum then autovacuum_work_mem will be used."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex | 2021-03-11 10:48:21 | Invalid idle_in_transaction_session_timeout data type |
| Previous Message | Bruce Momjian | 2021-03-11 01:27:06 | Re: advanced.sql tutorial script |