which one you mean ? I changed the threshold and the scale for
the specific table...
Going by the
block hits/misses/dirtied and the mentioned vacuum times,
it looks
like auto-vacuum is set to the standard settings and if so it
spent
about 100% of its time sleeping on the job.
It might be a better
idea to consider changing the vacuum settings
globally rather than
just for one table.
Running a vacuum_cost_limit of 200 is likely
something you'd not want
to ever do with modern hardware... well
maybe unless you just bought
the latest Raspberry PI, or something.
You should be tuning that
value to something that runs your vacuums
to a speed you're happy with
but leaves enough IO and CPU for queries
running on the database.
If you see that all auto-vacuum workers
are busy more often than not,
then they're likely running too slowly
and should be set to run more
quickly.