Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower.

Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> I actually wonder if instead of doing all the the hard way in C whether
> we should just use SPI for each worker to build it's list of tables. The
> big advantage that would provide is the ability for users to customize
> the scheduling, but I suspect it'd make the code simpler too.

By that you mean "user can write a SQL query that determines autovacuum
targets"?  -1.  That would bring us back to the bad old days where a
poorly-thought-out vacuum cron job would miss tables and lead to a
database shutdown.  Not to mention SQL injection risks.

If we need to improve autovac's strategy, let's do that, but not by
deeming it the user's problem.

            regards, tom lane