I have seen similar issues with other flags. Specifically, without careful consultation of the documentation, it is easy to misconfigure these parameters due to the varying default unit semantics.
This made me think about the vacuum failsafe mechanism. Although the failsafe successfully overrides certain cost and delay restrictions to speed up anti-wraparound vacuuming once a vacuum process kicks in, an accidentally high naptime creates a scheduling bottleneck. It prevents the launcher from initiating the autovacuum processes in the first place. Thanks, Virender
