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 1vdaVy-002VJN-2w for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Jan 2026 20:52:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vdaVw-00FSur-0T for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Jan 2026 20:52:20 +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 <3danissimo@gmail.com>) id 1vdaVv-00FSuh-2d for pgsql-hackers@lists.postgresql.org; Wed, 07 Jan 2026 20:52:20 +0000 Received: from mail-yx1-xb135.google.com ([2607:f8b0:4864:20::b135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from <3danissimo@gmail.com>) id 1vdaVu-004lpg-1K for pgsql-hackers@postgresql.org; Wed, 07 Jan 2026 20:52:18 +0000 Received: by mail-yx1-xb135.google.com with SMTP id 956f58d0204a3-64661975669so2671089d50.3 for ; Wed, 07 Jan 2026 12:52:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1767819137; x=1768423937; darn=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=w9LWxCLPidLLlZcm/Dny2/JPAdV4pn+DE4U/DlkLKSA=; b=H4R9N+6taAo8nJxArKvArXXMuuO/2ncr6TCMGcMXhMuv+hjMeo5MLuhV5Pl7ytP86G RXejQmR9poymKzbJlhg93abhgozvYIkTIoYkTXCxqEzQpm1XtEciHn8NwbnpQ6bvJgRZ /+L2h8bFzsZtS5QBuLSzXSVvtaiBsKlhNZsCYusZITUD4CE0MLiB+BRcLTIDLe+RqGtZ fdvKgwKBU3ThUm6knVqJ+GbuA67oQ/gQucAQMu86y5DJgAn58zBPTO7GLwiF23/FP4Ns 0rhHd3PJ5+T6IuRObp3PG+1GBEQgEKsK/hM80wYKidUKAXiLe9HEn1H0JUR8mKLZwl88 4BLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767819137; x=1768423937; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=w9LWxCLPidLLlZcm/Dny2/JPAdV4pn+DE4U/DlkLKSA=; b=t5v7S9zUbAQ2r8t/n8ZRd7AgOevt1+ihrpF32Cv5JueI4Jn8K+CP+m458jaNQFOTr4 Js0xojSwKfI8tZExuWim3dqAQGP9GziGE2xAy/haHR4n9qMUqtplq1RCZGgXgZo12DBu aSxvYESqvh6EEV+xCEP1Z/yR3ZPgPt8y365/iKhDJ/prmaH5Vm1MObSwoxqUG2KzjCwG 82eOPdzhFjQRJ2Ni/4Xev1HgFTK77G2MRxD/iy4WtU5UvhNnPrdJYEDXUXbiGS+3AgHL kGC/fY45V4n5m6OfMQavHnISb1u9p2QpxbPlnYqwLD1JZWA+RmhVeeaRd6gsDeqr3z8K qrAw== X-Gm-Message-State: AOJu0Yz9Qj3WqglyvpChA4i9VVnwbt33bnYaiyYYxfW76pV6tBXZmfLz DJYIC4CkteAnmcJzFk8nBhdNJ6lodbLDCeUUFkQO3Y0LWevkXE5wVffaJe3CQRXzDtiuFMWgP0Q QU56WWod96ivmdjhGlEZHiia2x47II7QGlune X-Gm-Gg: AY/fxX5/S3NxUXg0ovB1SIMZN2ciQ6xyK+1/wUcbI1wgx+XYDuphTm8ROJd+//8r4Bp GHNmXSfLNnKGqoIPVLhpnoLvm1P1Cn1etWpnPXO15G/L/Z9D4tYACZsBmBvGOBwxgoafHk4fXzO yXqMwBTbBjmXO/Fpf50ACTyr475O7fmVMV4RMAsvNynaj6NF4gwvf5hU9yCiXjeypCdquUXvY5v 35BKdAb1YtihHV/MLHvbs0w4IhAK0Okr0MtiUKviGxQDrjbeMcOE07Zwx8tGPQsvgRg X-Google-Smtp-Source: AGHT+IHOA512TQPChvWBwwypeT6P41j1zwWehPkvYdx+bV7Fp+NrOTlf3hDQUKpDrsid0AsvxxkeG3LDbJ//I6PbgKY= X-Received: by 2002:a05:690e:4144:b0:645:520d:31bb with SMTP id 956f58d0204a3-64716b8c293mr3211861d50.23.1767819137134; Wed, 07 Jan 2026 12:52:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniil Davydov <3danissimo@gmail.com> Date: Thu, 8 Jan 2026 03:52:04 +0700 X-Gm-Features: AQt7F2rSeJFQys6Oxhdp82m59FML5w0Erz4LqR55X4rEHLZPjDGBdLZFvztRG_A Message-ID: Subject: Re: POC: Parallel processing of indexes in autovacuum To: zengman Cc: pgsql-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 Hi, On Wed, Jan 7, 2026 at 8:51=E2=80=AFPM zengman wro= te: > > I noticed one thing: autovacuum_max_parallel_workers is initialized to 0 = in globals.c, > but its GUC default (boot_val) is '2' in guc_parameters.dat. While GUC ov= errides it on startup, > this mismatch may cause confusion. Perhaps we should modify this to match= the approach for max_parallel_workers. > Good catch, thank you! I'll fix it in the next version of the patch. -- Best regards, Daniil Davydov