Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4406364

Browse files
committed
Doc: improve v13 release note item about autovacuum and INSERTs.
The previous text was confusing, per off-list discussion with Bruce Momjian.
1 parent e62c5ea commit 4406364

File tree

1 file changed

+20
-8
lines changed

1 file changed

+20
-8
lines changed

doc/src/sgml/release-13.sgml

Lines changed: 20 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -762,16 +762,28 @@ Author: David Rowley <drowley@postgresql.org>
762762
-->
763763

764764
<para>
765-
Allow inserts, not only updates and deletes, to
766-
trigger <link linkend="autovacuum">autovacuum</link> activity
765+
Allow inserts, not only updates and deletes, to trigger vacuuming
766+
activity in <link linkend="autovacuum">autovacuum</link>
767767
(Laurenz Albe, Darafei Praliaskouski)
768768
</para>
769769

770770
<para>
771-
This new behavior reduces the work that will be necessary later
772-
when the table needs to be frozen, and it allows pages to be
773-
marked as all-visible sooner. All-visible pages allow index-only
774-
scans to access fewer heap rows.
771+
Previously, insert-only activity would trigger auto-analyze but
772+
not auto-vacuum, on the grounds that there could not be any dead
773+
tuples to remove. However, a vacuum scan has other useful
774+
side-effects such as setting page-all-visible bits, which improves
775+
the efficiency of index-only scans. Also, allowing an insert-only
776+
table to receive periodic vacuuming helps to spread out the work
777+
of <quote>freezing</quote> old tuples, so that there is not
778+
suddenly a large amount of freezing work to do when the entire
779+
table reaches the anti-wraparound threshold all at once.
780+
</para>
781+
782+
<para>
783+
If necessary, this behavior can be adjusted with the new
784+
parameters <xref linkend="guc-autovacuum-vacuum-insert-threshold"/>
785+
and <xref linkend="guc-autovacuum-vacuum-insert-scale-factor"/>, or
786+
the equivalent table storage options.
775787
</para>
776788
</listitem>
777789

@@ -782,8 +794,8 @@ Author: Thomas Munro <tmunro@postgresql.org>
782794
-->
783795

784796
<para>
785-
Add <xref linkend="guc-maintenance-io-concurrency"/> to control I/O
786-
concurrency for maintenance operations (Thomas Munro)
797+
Add <xref linkend="guc-maintenance-io-concurrency"/> parameter to
798+
control I/O concurrency for maintenance operations (Thomas Munro)
787799
</para>
788800
</listitem>
789801

0 commit comments

Comments
 (0)