> Good call. Here is an updated patch. thanks for the update!
After staring at the documentation for a while, I am now wondering whether we are adequately describing the rationale for this GUC. The GUC documentation mentions that this is a 'cap on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor,' which is acceptable; however, I think further elaboration is necessary in routine-vacuuming.html#AUTOVACUUM. This is because scale_factor and threshold are already well-known and widely understood parameters, and introducing a third one to the mix deserves a bit more of an explanation. What do you think? Based on my understanding of the discussion, the purpose of the GUC is to prevent large tables from experiencing extended periods without an autovacuum, particularly because scale_factor triggers vacuuming less frequently as the table grows. Currently, users can handle such cases by disabling (or lowering) autovacuum_vacuum_scale_factor and setting an appropriate autovacuum_vacuum_threshold; Therefore, this GUC becomes a more convenient and predictable way to ensure autovacuum triggers on a large table. Is this correct? Regards, Sami
