Hi Masahiko
> If we set
> it per-table basis, it’s useful when the user already knows which
> tables are likely to take a long time for autovacuum
I would assume that's the default case, most apps I've seen are designed
around a small
number of large tables that take up most of the maintenance
Hi Stephen
> ... can set vacuum options on a table level which autovacuum should
respect,
> such as vacuum_index_cleanup and vacuum_truncate. For skip locked,
> autovacuum already will automatically release it's attempt to acquire a
> lock if someone backs up behind it for too long.
This is
s for log spam, I'm not sure it's a problem as long as the verbose option
is disabled by default.
Tommy
On Fri, Jan 22, 2021 at 2:33 PM Tom Lane wrote:
> Tommy Li writes:
> > I was surprised to see that there's no way to get `VACUUM VERBOSE`-like
> > output from autovacuu
Hi all
I was surprised to see that there's no way to get `VACUUM VERBOSE`-like
output from autovacuum. Is there any interest in enabling this?
Additionally, is there any interest in exposing more vacuum options to be
run by autovac? Right now it runs FREEZE and ANALYZE, which leaves the
VERBOSE,
