diff options
| author | Alexander Korotkov <akorotkov@postgresql.org> | 2018-06-26 15:00:51 +0300 |
|---|---|---|
| committer | Alexander Korotkov <akorotkov@postgresql.org> | 2018-06-26 15:00:51 +0300 |
| commit | 6ca33a885bf892a7fa34020a2620c83ccec3cdd7 (patch) | |
| tree | a6864e0aa75999cad73918ca580e3f3f4e1bea4c /src/backend/executor/nodeModifyTable.c | |
| parent | c9301deb9bf86aaf9144a66026bc121a3eededee (diff) | |
| download | postgresql-6ca33a885bf892a7fa34020a2620c83ccec3cdd7.tar.gz postgresql-6ca33a885bf892a7fa34020a2620c83ccec3cdd7.zip | |
Increase upper limit for vacuum_cleanup_index_scale_factor
Upper limits for vacuum_cleanup_index_scale_factor GUC and reloption
were initially set to 100.0 in 857f9c36. However, after further
discussion, it appears that some users like to disable B-tree cleanup
index scan completely (assuming there are no deleted pages).
vacuum_cleanup_index_scale_factor is used barely to protect against
stalled index statistics. And after detailed consideration it appears
that risk of stalled index statistics is low. And it would be nice to
allow advanced users setting higher values of
vacuum_cleanup_index_scale_factor. So, set upper limit for these
GUC and reloption to DBL_MAX.
Author: Alexander Korotkov
Reviewed-by: Masahiko Sawada
Discussion: https://postgr.es/m/CAC8Q8tJCb%3DgxhzcV7T6ctx7PY-Ux1oA-AsTJc6cAVNsQiYcCzA%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions