Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pbSrA-0005v9-CP for pgsql-admin@arkaria.postgresql.org; Sun, 12 Mar 2023 21:03:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pbSr8-0007il-RE for pgsql-admin@arkaria.postgresql.org; Sun, 12 Mar 2023 21:03:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pbSr8-0007ic-DB for pgsql-admin@lists.postgresql.org; Sun, 12 Mar 2023 21:03:50 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pbSr1-0006bP-IB for pgsql-admin@lists.postgresql.org; Sun, 12 Mar 2023 21:03:50 +0000 Received: by mail-qt1-x835.google.com with SMTP id w23so11394301qtn.6 for ; Sun, 12 Mar 2023 14:03:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678655021; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=NXBeALmlNcELjNrFPkRh+n0n0j6UtT+49LKrXpZRCCg=; b=Qfp5rCXlnW5TQtGzDjYkci/rgfWZFDPorx3+CZfq28VyO/rBIzozYrgb1SB5m9ff+E cf5sGmQHxSmvrrK/PaS7OHOLgbMlTU3mr+0I1snBk7TDRpxmgiubhIsC3CBiVRkKg9/p nMsxV5s1U5HvlbroktDPPA+ENP5EMj0eB+YJPOrq8k1qQgoIWXYuInU5zfgLprhIr2rW Xa/WIcx4IhUhb9VzfKTgK2IE/MK8c9h6T1rf6cd8BaiHhlM1toK9bs4WQonUczdnnGNX Rk/p1gwdFNSIvYr+N1i/fy4064eGgoowyvtvdXZl56wsFLYuerdmqeknUx0mPvSZpBdj aZGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678655021; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=NXBeALmlNcELjNrFPkRh+n0n0j6UtT+49LKrXpZRCCg=; b=49AOZ9AodvREfucQ8QzudvO6Rf4qQd7dVVWtGfN+pOL8yXvAIaEFm+iPtrxUEKukhA TMijGz/4wY1Hsvh6ZUjIiOVvzSiNfHOixHQ0MWLCikrwuxbZUXxpSrC2cXxA+Zy2DUe8 dK+PfdGLh2XrFinwxuHBZOOgL42gKOSepsBfNYDGr++JqUhYYjwh4hewyQu/xPzWG2wv uuNon1RhpJZoKs5eNEv3MWl5F/BHsA4YF7R6IVbnmQwQMhbVrjLerFnP0JMSC62zoiWR J19wvukbL82w0D0+7mDTFBn4rQA+L783MsUQuJXhuoPLknlrou30gryHH5Pnbzpy5W+0 sw6w== X-Gm-Message-State: AO0yUKV4fRrsbWxcO9hQecLxRioKDEzPlN/OwA3vBUTcdPUNEJIsrT8z hYFOT4nPel8TZ8+6CEukVMjAvBXU/K0= X-Google-Smtp-Source: AK7set8akqJ67ZLkTTr9G2SkqaWSd85Xa9KVfsY2DzXoh1UqGj2QidaXWrclknLer2yaIpPKAg7uvw== X-Received: by 2002:a05:622a:174b:b0:3bf:d9d2:4866 with SMTP id l11-20020a05622a174b00b003bfd9d24866mr49394135qtk.24.1678655021388; Sun, 12 Mar 2023 14:03:41 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id s20-20020a37a914000000b00741a984943fsm4141253qke.40.2023.03.12.14.03.41 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 12 Mar 2023 14:03:41 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------xTwHEPpJc8JmET09jlOBiQP5" Message-ID: <886f6541-48d4-6b9b-c44a-1c2489c5f3fe@gmail.com> Date: Sun, 12 Mar 2023 16:03:40 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Tooling for per table autovacuum tuning Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <5c0a6ab9ba801e0fa7c2217e49ce804837c64cf1.camel@cybertec.at> <14072753.2216234.1678640212317@mail.yahoo.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------xTwHEPpJc8JmET09jlOBiQP5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 > 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. --------------xTwHEPpJc8JmET09jlOBiQP5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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.
--------------xTwHEPpJc8JmET09jlOBiQP5--