diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2021-03-11 12:42:46 -0800 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2021-03-11 12:42:46 -0800 |
| commit | effdd3f3b633e88feaa675377075f02ecc99aee4 (patch) | |
| tree | a55690b855700ef0f3276dda0e56c08eb58b396d /src/backend/access/nbtree/nbtutils.c | |
| parent | 32fd2b57d7f64948e649fc205c43f007762ecaac (diff) | |
| download | postgresql-effdd3f3b633e88feaa675377075f02ecc99aee4.tar.gz postgresql-effdd3f3b633e88feaa675377075f02ecc99aee4.zip | |
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@paquier.xyz
Diffstat (limited to 'src/backend/access/nbtree/nbtutils.c')
| -rw-r--r-- | src/backend/access/nbtree/nbtutils.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/backend/access/nbtree/nbtutils.c b/src/backend/access/nbtree/nbtutils.c index fdbe0da4720..d5243107239 100644 --- a/src/backend/access/nbtree/nbtutils.c +++ b/src/backend/access/nbtree/nbtutils.c @@ -2105,6 +2105,8 @@ btoptions(Datum reloptions, bool validate) { static const relopt_parse_elt tab[] = { {"fillfactor", RELOPT_TYPE_INT, offsetof(BTOptions, fillfactor)}, + {"vacuum_cleanup_index_scale_factor", RELOPT_TYPE_REAL, + offsetof(BTOptions, vacuum_cleanup_index_scale_factor)}, {"deduplicate_items", RELOPT_TYPE_BOOL, offsetof(BTOptions, deduplicate_items)} |