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.94.2) (envelope-from ) id 1v6YGk-006LUS-La for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Oct 2025 17:48:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v6YGi-00C5vh-82 for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Oct 2025 17:48:05 +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.94.2) (envelope-from ) id 1v6YGh-00C5vW-V0 for pgsql-hackers@lists.postgresql.org; Wed, 08 Oct 2025 17:48:04 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v6YGg-000i0Z-0V for pgsql-hackers@postgresql.org; Wed, 08 Oct 2025 17:48:03 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-37612b15a6aso479311fa.2 for ; Wed, 08 Oct 2025 10:48:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759945681; x=1760550481; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ACUKh/VeHDTR1gMLn2nPQ3EqwWkaCXUMf7/VtYTzQSQ=; b=LAg8QGjDm2lffBRKv7qRJ6xBY99/fD2CqucqYwLUKBxBZhhigoKKTVfQ4H+D7Y/+rK /AxkGOel47su3pVUWKSGGVD95rmwkx68ZvhadXgikiTQO1rwEwQlKti43nb2JNjtgWfJ g0Su7oyyoKzqoDKpq9d8xUxnoetiGBWade4nEvp4pqy8jB62+FMo4atgie8xA/wdIjfk Tlioe7NM9ZNIZ6MViscqlXX9+hTdY+JxXrIIqxvNoHMyj/NhTzUFpFoU2YxqZbazgG7q v5rTZrE1BnqIoHZ0LAWLwDS4dbY9ZRPZJ8aJcs75JMQhPJAzqNi+J4e6e6Mt7RQsfhVb 8QvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759945681; x=1760550481; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ACUKh/VeHDTR1gMLn2nPQ3EqwWkaCXUMf7/VtYTzQSQ=; b=Y2169uau/6jC0+PvpHNq43drhUbrkeuox/0o5yZ7WB4uK47W6MdyzsNqiNO9ObfD4D kUx8BpqU0s928/ZVbev5j0SuaHwiGZOi/E3WA+f5o60N128DWa1CHHuKjFQNm4AAhsC9 QOw+D8EXG6TzD450JRxT8NZYcZ7zO4VYIMqWyAAFwj9t/GVfKvwNLEu4VIYgSKekVGFS +XFm3H+zA+uWMeUnMX5PzZQD3Wl9ZpxnPgFc8mu2GwJ2rHruml9d78lMZ5+MpNIysp0V 9HYaMfVALoNB34NQEnJ0bFkl/PoGGO1ppKcMlR6bBU8UW9ILdWrkknYMIv78tDIGhtOh Bzsw== X-Gm-Message-State: AOJu0YzKE5YjfugxamSwK+Q6WOnQ37nHpGOWpZiZ7Jh+sNVVqiyFm3ni 2+Lk07HRj/Jmo0QlPVLvc3+EjzYEJ0tq/kVfilgPB2j/Z2fCr9i0s5SbJ1K7bzZxKJmNRy55g4s SOs7DPZd3H+hz23u/J+KUBkK+OSmebNQ= X-Gm-Gg: ASbGnctgLd45OB/Kv9HPfmxEqXdSsqrCIV0SEBhDxE0GGMknLbCgkfaJDv7elwoQ8P9 ERzzXt5WP4/xXXn7QaUbhxYvBHOu+IVRa6IAgmr21xcKMbSQlbGpGAzCJdYHl0Zn130KDgGbkn6 yU+vw08g+LFdoRwReeMGCUpQv2lmwIb/RsLx4l/Z9FrQJJvBBvzpStAhmZZ6ZECqyPCDHzUunWh TvXr3dA6zKfNwY6Y1FZ/DXij+SPVPA= X-Google-Smtp-Source: AGHT+IGgW/0A886cUD7AwK77rh2dVMwAuXjBrtmVZ9nuKXz4UkR/NX2+O7uyp9BwJNaebRooFcAnq4KP74FVapzBGqE= X-Received: by 2002:a05:651c:1586:b0:355:b3ec:11e2 with SMTP id 38308e7fff4ca-37609c9caddmr10872431fa.8.1759945681174; Wed, 08 Oct 2025 10:48:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sami Imseih Date: Wed, 8 Oct 2025 12:47:50 -0500 X-Gm-Features: AS18NWD069NQqCVB4DoMZmB5mLirD6qHv44zvYH8QQ-g-BjeM0-Jm17j1noDFpI Message-ID: Subject: Re: another autovacuum scheduling thread To: Nathan Bossart Cc: pgsql-hackers@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Not saying that the current approach, which is as you mention is > random, is any better, however this approach will likely increase > the behavior of large tables saturating workers. Maybe it will be good to allocate some workers to the oldest tables and workers based on some random list? This could balance things out between the oldest (large) tables and everything else to avoid this problem. -- Sami Imseih Amazon Web Services (AWS)