mirror of
https://github.com/postgres/postgres.git
synced 2025-04-24 10:47:04 +03:00
doc PG 17 relnotes: add item about vacuum storage/limits/WAL
Reported-by: Alvaro Herrera Discussion: https://postgr.es/m/202405150838.sg5ddcexyyf4@alvherre.pgsql Backpatch-through: master
This commit is contained in:
parent
4dd29b6833
commit
a8010d03e1
@ -519,6 +519,25 @@ Allow vacuum to more efficiently remove and freeze tuples (Masahiko Sawada, John
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<!--
|
||||
Author: Masahiko Sawada <msawada@postgresql.org>
|
||||
2024-03-21 [30e144287] Add TIDStore, to store sets of TIDs (ItemPointerData) ef
|
||||
Author: Masahiko Sawada <msawada@postgresql.org>
|
||||
2024-04-02 [667e65aac] Use TidStore for dead tuple TIDs storage during lazy vac
|
||||
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
|
||||
2024-04-03 [6dbb49026] Combine freezing and pruning steps in VACUUM
|
||||
-->
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Allow vacuum to more efficiently store tuple references and remove its memory limit (Masahiko Sawada, John Naylor)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Specifically, maintenance_work_mem and autovacuum_work_mem can now be configured to use more than one gigabyte of memory. WAL traffic caused by vacuum is also more compact.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<!--
|
||||
Author: Robert Haas <rhaas@postgresql.org>
|
||||
2024-01-18 [c120550ed] Optimize vacuuming of relations with no indexes.
|
||||
|
Loading…
x
Reference in New Issue
Block a user