On Mon, 2020-06-15 at 16:42 +0300, Kristjan Mustkivi wrote:
> > You should schedule down time and run a VACUUM (FULL) on that table.
> > That will rewrite the table and get rid of the bloat.
>
> But in order to avoid the situation happening again (as it will with
> the current settings), I should likely make the autovacuuming on the
> TOAST table even more aggressive via
> toast.autovacuum_vacuum_scale_factor tinkering, right?
No, the correct way is to reduce "autovacuum_vacuum_cost_delay".
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
