On Wed, Apr 5, 2023 at 3:44 PM Melanie Plageman
<melanieplage...@gmail.com> wrote:
> VacuumUpdateCosts() also calls AutoVacuumUpdateCostLimit(), so this will
> happen if a config reload is pending the next time vacuum_delay_point()
> is called (which is pretty often -- roughly once per block vacuumed but
> definitely more than once per table).
>
> Relevant code is at the top of vacuum_delay_point():
>
> if (ConfigReloadPending && IsAutoVacuumWorkerProcess())
> {
> ConfigReloadPending = false;
> ProcessConfigFile(PGC_SIGHUP);
> VacuumUpdateCosts();
> }
Yeah, that all makes sense, and I did see that logic, but I'm
struggling to reconcile it with what that comment says.
Maybe I'm just confused about what that comment is trying to explain.
--
Robert Haas
EDB: http://www.enterprisedb.com
