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 1uAyXU-004nAr-Ew for pgsql-hackers@arkaria.postgresql.org; Fri, 02 May 2025 22:07:24 +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 1uAyXS-00BvsO-45 for pgsql-hackers@arkaria.postgresql.org; Fri, 02 May 2025 22:07:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uAyXR-00Bvrn-R2 for pgsql-hackers@lists.postgresql.org; Fri, 02 May 2025 22:07:22 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uAyXQ-000lqr-1R for pgsql-hackers@lists.postgresql.org; Fri, 02 May 2025 22:07:22 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-30db1bc464dso21815961fa.0 for ; Fri, 02 May 2025 15:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746223638; x=1746828438; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=zsbJYMsrqYb+jUalKguHYJqhniMh7x8j/pd2caYOBz0=; b=huhUC68C5AJl234k3Hn6MmvX4PVcs4lt99qmnPi6NvFWouJMUXciHYsc/iH/G7qA6a MdezDvsMbFbs8EpakQQqOO9HlCDDrTJotrlWiCbGLRWZwYhJaYix+VeSlYnUWVhBeMry uRVFKJ84mj/8gk62VTds/YUgO3GrtGKaW0YsMD1Lq7xxRyNzX5kbzOaZVfO0V9D4v4rr O++3Z3naPVXvWp1UNNE1jUdoNlSQl9yOA2asVKsPMA/awW7sXgk3o5NDR2iH49iRaDoB bvUVcQHxYwzFPQo1SKt1HfWoTehdygNjfNCstDl+sLQWktlFaEA4Z8dy9iWQCiHKGk02 WSJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746223638; x=1746828438; h=content-transfer-encoding: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=zsbJYMsrqYb+jUalKguHYJqhniMh7x8j/pd2caYOBz0=; b=o0keQSqr/o5m3CdxRNAGHzww2999webj65pUhKu23Oh+JxbDp9Q8ysifzy0nkM77LQ SKogxq5Rznk8E0vDXQz/NGeW8vnDiTP5wNlzS61TlAFrXx1xdI7v7VyvqB2SYvo0sWh1 Chocvs9eC1PMzW3k+iE0DOhVw0q1anIwKXWrlGEZ5ZPWwNvzKMaQ3w6/FgDu+SJmJ8Oo RBY6njY5pwZn9cKdJGy6ssl0x1dXy2O8zWkrjTFrJouLp+nI+Qm4nXoniCFOfCEpFMir u7J4qNCzfcPiNr9IXicxZnk2O5OpqbHMhKoslZ9/3XB3RMmsl+ZqWeqNo70VUmRtremq rW5A== X-Forwarded-Encrypted: i=1; AJvYcCXGcxshVlOnFlCicO4ZNSvXqqRasEtmDBueWhCjGhGIjbixRpX7sPfmjoY25pbqwMmG/6RO90M2+MJWzN3m@lists.postgresql.org X-Gm-Message-State: AOJu0YyKSy3qqTChi3+Xgu2DlaAdpWtQLk4pquofRNQXTPtL7XH840GG bS4lI5waJ+r9AE1bQWVVwf7tTJUzvx9MEyjaj/V/2V/82fDP5H0qtYAhhBRSF/0/SqrNKgCoQ5o fuWobxOmgGTyrS6GheXaMNSKERZo= X-Gm-Gg: ASbGncuFHL/RbvtkXXFXA202PMGZsp7SBlOB15VhG1ccyK2lKRub9NSOLKxdClmnyl7 IsqtZYTP0ZuFmdX6Rj20xK+96SMA7bPKpdoge0ocBq7hsKs54SgibWjjz9EkG4OJrNc8Bsrahhy GoORTQLodcHd6yQjar5NIjWLPV27XMsB8/sw== X-Google-Smtp-Source: AGHT+IFg1zMaovHcaI7jZNoEwdW5tpYuJLTkPtH4KdqVCaQHRsU3iVH8mhONyfNCKa0zdaTGQY2E6GPT+mG4q5WzVRg= X-Received: by 2002:a05:651c:1441:b0:30b:b987:b676 with SMTP id 38308e7fff4ca-321daae5f29mr2493221fa.2.1746223638094; Fri, 02 May 2025 15:07:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Masahiko Sawada Date: Fri, 2 May 2025 15:06:41 -0700 X-Gm-Features: ATxdqUE2Fvj5kLaJs0CxTBTC0u5vvuZGG9uVOr-C-ck851J3NJANGapdwcg07Z4 Message-ID: Subject: Re: POC: Parallel processing of indexes in autovacuum To: Sami Imseih Cc: Maxim Orlov , Postgres hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, May 2, 2025 at 9:58=E2=80=AFAM Sami Imseih wr= ote: > > > Once we have parallel heap vacuum, as discussed in thread[1], it would > > also likely be beneficial to incorporate it into autovacuum during > > aggressive vacuum or failsafe mode. > > IIRC, index cleanup is disabled by failsafe. Yes. My idea is to use parallel *heap* vacuum in autovacuum during failsafe mode. I think it would make sense as users want to complete freezing tables as soon as possible in this situation. Regards, --=20 Masahiko Sawada Amazon Web Services: https://aws.amazon.com