From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Joseph Hammerman <joe.hammerman@datadoghq.com>
To: Wolfgang Wilhelm <wolfgang20121964@yahoo.de>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Tooling for per table autovacuum tuning
Date: Mon, 13 Mar 2023 06:58:44 +0100
Message-ID: <16d61d864feda279cfa6bcb4ea4d50c2b4fa3a7f.camel@cybertec.at> (raw)
In-Reply-To: <CAHs7QM_dDN3M=G0vEEi7V_wZaWmtJO5OK6ruh7bBfQ4BNo4QxQ@mail.gmail.com>
References: <CAHs7QM_scGEh8uhsCUoc_BEimyYsUTVZxpE10rUiqnShd8nTkQ@mail.gmail.com>
<5c0a6ab9ba801e0fa7c2217e49ce804837c64cf1.camel@cybertec.at>
<14072753.2216234.1678640212317@mail.yahoo.com>
<CAHs7QM_dDN3M=G0vEEi7V_wZaWmtJO5OK6ruh7bBfQ4BNo4QxQ@mail.gmail.com>
On Sun, 2023-03-12 at 13:34 -0700, Joseph Hammerman wrote:
> What I am imagining is per table tuning that buckets the tables based on their relative sizes.
>
> Something like:
>
> Up to 1Gb - Small
> Up to 4Gb - Medium
> Up to 8Gb - L
> Bigger - XL
>
> And an accordant autovacuum_scale_factor associated with each size.
>
> The motivation for this is to make sure large tables get regularly vacuumed.
I understand.
There is no such option currently. Perhaps you can use "autovacuum_vacuum_threshold"
for something like that: if you set it to a certain (high) value and set "autovacuum_vacuum_scale_factor"
to 0, autovacuum is triggered based on the absolute number of dead tuples.
But I would say that the standard configuration makes sense in this case: normally,
large tables don't need to be vacuumed that often, and vacuum on large tables is
nore expensive too.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, joe.hammerman@datadoghq.com, wolfgang20121964@yahoo.de, pgsql-admin@lists.postgresql.org
Subject: Re: Tooling for per table autovacuum tuning
In-Reply-To: <16d61d864feda279cfa6bcb4ea4d50c2b4fa3a7f.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox