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 1kJYE4-0003nS-6K for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Sep 2020 08:28:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kJYE2-0003HZ-4E for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Sep 2020 08:28:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kJYE1-0003HR-4f for pgsql-hackers@lists.postgresql.org; Sat, 19 Sep 2020 08:28:05 +0000 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kJYDt-00077x-GF for pgsql-hackers@postgresql.org; Sat, 19 Sep 2020 08:28:03 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id 4DC29A8F for ; Sat, 19 Sep 2020 04:27:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 19 Sep 2020 04:27:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=3WhGep sOHOSB6oVJOpgk5TK5zzuW8TcKefv++IJxGz4=; b=p+GmjSweA7D3/bPhBQw6OA klp/qOcFjbiArIAMV4BwVIRgODT8ZK1XijP9toJTZn0DbFBrDCvvdMX+DfqUwPhI ZMUuzoAgl0gPAdvnY1xY//zW1ErsDMttJRItSqngpkEMVI+dzKgJ772uu0SEwHhH 5dsCoo7chC6TKyUBdtxKyfjhfYSOMWP9mMzluczII5ILVUhYnulR5RSJmGoGQZo7 lhQQ1PIKao7TM1ph8oo53QKxghfC/TmI5OsiIMfvrY/jBSLmm6JtU4oTNNgwnGRH s4nvpUYb5qDtpImAeHVPhWXJ9PfASU4OoDLvRd8rY1SSHd36hpQaZ+cOWM+YNERA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrtdekgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepvffhufhokffffgggtgfgsehtjeertd dtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgv ihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvg hrnhepteefvdfgjeeuieevgfffgeejtedtheduieekveffledugedtgeeigeffleevgfdv necuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgtohhmnecukfhppeekjedrudejje drjeeirdeileenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p57b14c45.dip0.t-ipconnect.de [87.177.76.69]) by mail.messagingengine.com (Postfix) with ESMTPA id 438AB3064674 for ; Sat, 19 Sep 2020 04:27:54 -0400 (EDT) To: pgsql-hackers From: Peter Eisentraut Subject: VACUUM PARALLEL option vs. max_parallel_maintenance_workers Organization: 2ndQuadrant Message-ID: <36aa8aea-61b7-eb3c-263b-648e0cb117b7@2ndquadrant.com> Date: Sat, 19 Sep 2020 10:28:59 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk If I read the code correctly, the VACUUM PARALLEL option is capped by the active max_parallel_maintenance_workers setting. So if I write VACUUM (PARALLEL 5), it will still only do 2 by default. Is that correct? The documentation (VACUUM man page) seems to indicate a different behavior. I haven't been able to set up something to test or verify this either way. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services