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 1pK0hd-0000x3-4P for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jan 2023 17:33:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pK0hc-0006TY-1p for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jan 2023 17:33:52 +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 1pK0hb-0006TP-P4 for pgsql-hackers@lists.postgresql.org; Mon, 23 Jan 2023 17:33:51 +0000 Received: from wnew4-smtp.messagingengine.com ([64.147.123.18]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pK0hZ-0004Dx-Eu for pgsql-hackers@postgresql.org; Mon, 23 Jan 2023 17:33:50 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id F04AD2B06835; Mon, 23 Jan 2023 12:33:47 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 23 Jan 2023 12:33:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1674495227; x=1674502427; bh=g EU6cDlQhLtBWGu7T7iaUjL+7/whYLlCrlGM0o4ruEY=; b=pKc9i2iDYeXBhtniC U3stnC7ze860M8f8rtsqJppWQeBp4gM4tWFq9OtrPj60n0P36814PnFA6iNWnJTF DBQ+FjEoczJAGXCZJ6MxNrD+86geofxuk/Stpl0QcgMvFDu6y4DnoAO5ZEgtLL1Y 3Rep05azyc6HKYu7HfGGZ7yfPxTU+pQwvWgAum/4HUcKn6xolZVdzEcbmA2WrcBh /bCsT0I9nzWGBACgQpB4vMr207H5feHCfWFEravntApntseNxBqy8bP/0DvPvAYd Us3O8WNTd8xnyZMesaUs/JuXI75eboH3De/8mPAFRwdbjn0fYhfDM/GIWoO4ioAC L/yEQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddukedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 23 Jan 2023 12:33:47 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 921F79A; Mon, 23 Jan 2023 18:23:20 +0100 (CET) Date: Mon, 23 Jan 2023 18:23:20 +0100 From: Alvaro Herrera To: "Mead, Scott" Cc: "pgsql-hackers@postgresql.org" Subject: Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay Message-ID: <20230123172320.cokmhkmgd3743wxc@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0A3F8A3C-4328-4A4B-80CF-14CEBE0B695D@amazon.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Feb-08, Mead, Scott wrote: > Hello, > I recently looked at what it would take to make a running autovacuum > pick-up a change to either cost_delay or cost_limit. Users frequently > will have a conservative value set, and then wish to change it when > autovacuum initiates a freeze on a relation. Most users end up > finding out they are in ‘to prevent wraparound’ after it has happened, > this means that if they want the vacuum to take advantage of more I/O, > they need to stop and then restart the currently running vacuum (after > reloading the GUCs). Hello, I think this has been overlooked, right? I can't find a relevant commit, but maybe I just didn't look hard enough. I have a feeling that this is something that we should address. If you still have the cycles, please consider posting an updated patch and creating a commitfest entry. Thanks -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Someone said that it is at least an order of magnitude more work to do production software than a prototype. I think he is wrong by at least an order of magnitude." (Brian Kernighan)