Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJKcd-001y6c-1T for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Nov 2025 23:51:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJKcZ-00FEAW-2q for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Nov 2025 23:51:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJKcZ-00FEAH-1Q for pgsql-hackers@lists.postgresql.org; Wed, 12 Nov 2025 23:51:27 +0000 Received: from mail-yx1-xb12c.google.com ([2607:f8b0:4864:20::b12c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJKcX-006oXo-2J for pgsql-hackers@postgresql.org; Wed, 12 Nov 2025 23:51:26 +0000 Received: by mail-yx1-xb12c.google.com with SMTP id 956f58d0204a3-640c857ce02so202333d50.0 for ; Wed, 12 Nov 2025 15:51:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20230601.gappssmtp.com; s=20230601; t=1762991485; x=1763596285; darn=postgresql.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=LUsIcb/LUXZLM8p0qPhEiG1pJKPywc1be7WgsFwmXl8=; b=o+E2D3KPqAWGrSJ9iHu6ltHogx+0w1PYCYIY5jjcadbycmrmYJBvvFO5B/LATEGd76 U/cDbTXDgadfjSknXdIWf0vc3Par0leLEiYSD5nyHBy1f8ULpyAhQeAnsoNeN1KGsLkK tRg9hR+oQp9Sj3L7QcobmWC4Vdpa1XfXIHT5Lw2lzonEZ6OYxUE3NJ7Kgiqr2R4mzyZH k4yA/DCi0LMd+MfPmWrxL5JvP34eoykygTEEt+1C9QXSXj8uiNkJ10NVBHEuSZAyG0x2 0BDXfQbyHaNwQRXAve7mw2p5zPWlkF4vqR+5FI3Ck8Vfygatdyriu1kPS/WB8ElkstOe /JDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762991485; x=1763596285; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=LUsIcb/LUXZLM8p0qPhEiG1pJKPywc1be7WgsFwmXl8=; b=lazYiPS8PwgGMC+rwFQSUj2bcPQLEPLXcB1kPIQZBZAqI0vEjApiMwEBWs2y0pKZc+ e+H/zO+eq1c7VsQE19dVrhB8FIpx7J76ajFS6kM0+GAJ5lJ6hKtTjBetY9Nmfhvfxe6n NZPRuGZutmKTeo3GQ2IRoMIe3v6OxTqmcZYDXLncAodYWX5QxeJK2T+cw0OPNL5U7USu XQG0ccFhR2bj82Uc9n7njYp+EmV9BrotEHVm1+qdBu1L7nclely/lZzk+SijG8GHCOLq 64N8FkIzB0PvqCPf/1tRlxF2gopd6y9Ba+k8uxT9Nu/xcJRjBniXLdXrbxz+LI3lFE9k SAnA== X-Forwarded-Encrypted: i=1; AJvYcCU4UQu2jKZuMliR26e/t2PhaW6eb75zg1Zcdze8AIuwKwHAJXKxt6WfQ7G7ewBg2hqtsB4xk3x9WHlGB70z@postgresql.org X-Gm-Message-State: AOJu0Yz0n/ML3c8423LV0mdffVSll6R/A6pI6ybE5H9MKxL1MRbTQfAm G6qTL+DlFZNEK/HDRDycRdw698YYYWmlk2XtgGxQlq+tmewNU8j54aHBu+d9aDljSg== X-Gm-Gg: ASbGncsuhIO3CSKNGkhgcIxxhbvMaDzcPJf3TBgE6acA+3ZwegeLFzKYPJ5PFRS2uN4 m92Yh68hnXnaIPtqTtnD7kbO/ijqSkCADHIVDDldFZWlZZ7Gp7BXrch2Tu5y7L8mxj/Tn6r85Pu bTTu2vtuBV1Fl16WUfoBEWn2aZprdctSNvCmZTSaypY6qBBkI5sOk3LcVbFzBONL8/WZ1ZgyLg9 VxSAqRxSTgJZjXPm+dWJQBt2iJBWYXsE6BonCDpYAhoihzyXlj/BhKeIrn9OX/tN7Dx0hShisHA thpu7uAxc2Yj81StQBywkNB4BsK4+gp9yIfJccuP0AsMbXs1cHSHOel7AiXeUlIoMoixLNcXnIu 2OGqK3pomD4d/7F/c2jgRO0svvhd0dZ4j5DiVdQH0MUDoLB+XdbKzvFhQNCsNnrNC8nQHxqkGsY NgKlKnF6yA9zvl73nHme1b6s++qpZs8v0u X-Google-Smtp-Source: AGHT+IEZagGaKTLMA+G8Kb76bUJwa78gJdsTveLyYEu9+4IEFWdxL+/XNYeSIEKdTaFvarvibJBfaQ== X-Received: by 2002:a53:c041:0:20b0:63f:ad6d:cbd5 with SMTP id 956f58d0204a3-64101b619cdmr3474228d50.60.1762991484932; Wed, 12 Nov 2025 15:51:24 -0800 (PST) Received: from smtpclient.apple ([2600:381:2214:e0ff:a817:ec39:fae3:8201]) by smtp.gmail.com with ESMTPSA id 00721157ae682-78822124b07sm1519147b3.30.2025.11.12.15.51.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 12 Nov 2025 15:51:24 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Jeremy Schneider Mime-Version: 1.0 (1.0) Subject: Re: another autovacuum scheduling thread Date: Wed, 12 Nov 2025 18:51:13 -0500 Message-Id: References: Cc: Nathan Bossart , Robert Treat , David Rowley , Robert Haas , pgsql-hackers@postgresql.org In-Reply-To: To: Sami Imseih X-Mailer: iPhone Mail (22H31) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Nov 12, 2025, at 5:10=E2=80=AFPM, Sami Imseih wro= te: >=20 > =EF=BB=BF >>=20 >> I do think re-prioritization is worth considering, but IMHO we should lea= ve >> it out of phase 1. I think it's pretty easy to reason about one round of= >> prioritization being okay. The order is completely arbitrary today, so h= ow >> could ordering by vacuum-related criteria make things any worse? >=20 > While it=E2=80=99s true that the current table order is arbitrary, that ar= bitrariness > naturally helps distribute vacuum work across tables of various sizes > at a given time >=20 > The proposal now is by design forcing all the top bloated table, that > will require more I/O to vacuum to be vacuumed at the same time, > by all workers. Users may observe this after they upgrade and wonder > why their I/O profile changed and perhaps slowed others non-vacuum > related processing down. They also don't have a knob to go back to > the previous behavior. >=20 > Of course, this behavior can and will happen now, but with this > prioritization, we are forcing it. >=20 > Is this a concern? It=E2=80=99s still possible to tune the cost delay, the number of autovacuum= workers, etc - if someone needs to manage too much autovacuum I/O concurren= cy and dialing it back down a little bit. I think that=E2=80=99s sufficient -Jeremy