0
(no delay). For busy production systems, set to 10-20ms
to balance vacuum progress with system responsiveness. For systems with significant I/O contention, consider 50-100ms
. Adjust based on your workload patterns and vacuum requirements.200
is generally appropriate. For systems where vacuum needs to be more aggressive, increase to 400-600
. For environments where minimal disruption is critical, decrease to 100-150
. Monitor vacuum progress and system performance when adjusting this value.20
is reasonable. This should typically be the highest of the page cost parameters since writing dirty pages is the most expensive operation. Increase if you need to be more conservative about write operations during vacuum.1
is appropriate. This should be the lowest of the page cost parameters since buffer hits are the least expensive operations. Generally, this value doesn't need adjustment unless you have specific memory characteristics.10
provides a good balance. This should be between vacuum_cost_page_hit and vacuum_cost_page_dirty in value. Adjust if your storage system has unusual read characteristics compared to write performance.Start your journey toward a healthier PostgreSQL with pghealth.
You can explore all features immediately with a free trial β no installation required.
π Start Free Trial