From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Add back vacuum_cleanup_index_scale_factor parameter. |
Date: | 2021-03-11 20:43:35 |
Message-ID: | E1lKS9f-0005Ea-UA@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Add back vacuum_cleanup_index_scale_factor parameter.
Commit 9f3665fb removed the vacuum_cleanup_index_scale_factor storage
parameter. However, that creates dump/reload hazards when moving across
major versions.
Add back the vacuum_cleanup_index_scale_factor parameter (though not the
GUC of the same name) purely to avoid problems when using tools like
pg_upgrade. The parameter remains disabled and undocumented.
No backpatch to Postgres 13, since vacuum_cleanup_index_scale_factor was
only disabled by REL_13_STABLE's version of master branch commit
9f3665fb in the first place -- the parameter already looks like this on
REL_13_STABLE.
Discussion: https://postgr.es/m/YEm/a3Ko3nKnBuVq(at)paquier(dot)xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/effdd3f3b633e88feaa675377075f02ecc99aee4
Modified Files
--------------
src/backend/access/common/reloptions.c | 9 +++++++++
src/backend/access/nbtree/nbtutils.c | 2 ++
src/include/access/nbtree.h | 1 +
3 files changed, 12 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2021-03-11 20:55:24 | Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM. |
Previous Message | Alvaro Herrera | 2021-03-11 20:39:21 | Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM. |