pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Tooling for per table autovacuum tuning
Date: Sun, 12 Mar 2023 16:03:40 -0500
Message-ID: <886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com> (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>

A giant table which is never updated (or deleted from) doesn't need to be 
vacuumed.

That same giant table which isn't added to anymore doesn't need to be 
analyzed, either.

On 3/12/23 15:34, Joseph Hammerman wrote:
> Hi all,
>
> Apologies for any confusion I may have caused. 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 hope that clears thing up!
> Joe
>
> On Sun, Mar 12, 2023 at 9:56 AM Wolfgang Wilhelm 
> <wolfgang20121964@yahoo.de> wrote:
>
>     I think Mr Hammerman is referring to T-shirts for user stories.
>
>     But even when I'm right I don't get what is meant with that. I don't
>     get what Joe means with "autovacuuming profiles per table". Joe, can
>     you elaborate on that?
>
>     Yours
>     Wolfgang
>
>     Am Sonntag, 12. März 2023 um 14:47:42 MEZ hat Laurenz Albe
>     <laurenz.albe@cybertec.at> Folgendes geschrieben:
>
>
>     On Sat, 2023-03-11 at 10:49 -0800, Joseph Hammerman wrote:
>
>     > I would like to define t-shirt sizes and have an
>     autovacuuming profile associated with each t-shirt size.
>     >
>     > Is there any tooling out there that assists in the execution side of
>     this? Or are all of you rolling your own?
>
>
>     Isn't that question 21 days early?
>
>     Yours,
>     Laurenz Albe
>
>
>

-- 
Born in Arizona, moved to Babylonia.

view thread (11+ messages)  latest in thread

Message-ID: <886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com>
Permalink:  ../886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com/
Also on:    postgresql.org/message-id/886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com

 · 

reply

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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Tooling for per table autovacuum tuning
  In-Reply-To: <886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com>

* 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