> One nit, please feel free to ignore it. VacuumUpdateCosts() prints
> yes/no for booleans, so on/off here could match that for consistency.
> AFAICS, there is no hard rule, and I am fine with it as is.

Better to be consistent here. Attached is v3-, which also updates the test
output expected.

--
Sami Imseih
Amazon Web Services (AWS)

Attachment: v3-0001-Propagate-track_cost_delay_timing-to-parallel-aut.patch
Description: Binary data

Reply via email to