Re: TOAST table size in bytes growing despite working autovacuum

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Kristjan Mustkivi <sonicmonkey(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: TOAST table size in bytes growing despite working autovacuum
Date: 2020-06-15 14:39:50
Message-ID: c3328713d6216fdbb7f5bf2d2693c0f93f550548.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Niels Jespersen 2020-06-15 15:04:03 SV: SV: pg_service.conf and client support
Previous Message Don Seiler 2020-06-15 14:07:17 Re: Mixed Locales and Upgrading