Apply data-checksum worker throttling parameters The DataChecksumsWorker accepts cost_delay and cost_limit parameters from pg_enable_data_checksums() so users can throttle the I/O caused by enabling checksums. Due to the API for setting the cost parameters changing between when the code was written, and when it was committed the new cost update function call was omitted and thus the parameters were silently ignored.
Fix by calling VacuumUpdateCosts() after assigning the parameters (both during worker startup and on the runtime cost-update path), and by leaving the page-cost weights at their GUC-controlled defaults. Author: Satyanarayana Narlapuram <[email protected]> Reviewed-by: Daniel Gustafsson <[email protected]> Reviewed-by: Ayush Tiwari <[email protected]> Discussion: https://postgr.es/m/cahg+qdeevh6atywdxybjw0womfozy66gdi5tfink_dxecrh...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/9a39056c418c83f164a25c8c2ee34600da99bfc7 Modified Files -------------- src/backend/postmaster/datachecksum_state.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
