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 1sI7yT-00DJ7A-Nw for pgsql-general@arkaria.postgresql.org; Fri, 14 Jun 2024 14:32:18 +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 1sI7yQ-001hTF-G2 for pgsql-general@arkaria.postgresql.org; Fri, 14 Jun 2024 14:32:15 +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 1sI7yP-001hNk-1y for pgsql-general@lists.postgresql.org; Fri, 14 Jun 2024 14:32:15 +0000 Received: from wfhigh4-smtp.messagingengine.com ([64.147.123.155]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sI7yL-001e3l-Lk for pgsql-general@postgresql.org; Fri, 14 Jun 2024 14:32:12 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id 4BD3D1800146; Fri, 14 Jun 2024 10:32:05 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 14 Jun 2024 10:32:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1718375525; x=1718461925; bh=RznF9/SNs0S3+3OLsz5T3/M/RjAI6yj8447Cn4NZ4V0=; b= qBtA/AOB2gDRzsvWixDdmOwSF/Etnzb4Ylm83zsAvP4NuU9O0hHkAN7OCSSxegCu qOS/UQG+AL6UDUPktxuh8AbEy6Ut4u0zMCYcTaVGfwo2K932Udx1i4pBwwOZAy73 wrn5gl0O3bpszqJ594+DckG6Psc7rY4rgwTO1RdvgKMTJ0FkzC4PnHqMrXRvcR0q SHcVx0wF/QGFOmjLZqW9jgDdtAv3kcQesa3tG0ORCWGPvTPcNGB9Kl2kj3cxQtkT +vGxqtpCMPTs7Y1OKiCVEzKcZlFMmCVMVXM4+wgcAI0n1s3Nyrbx53v2Q4q3ZhVV sSphFfmOjBYlf2NA0A1+9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1718375525; x= 1718461925; bh=RznF9/SNs0S3+3OLsz5T3/M/RjAI6yj8447Cn4NZ4V0=; b=C 7niDjq8wRTVoanV31GELDbWEcBcRVEZMFptyYMkxzFGX2tlGuHwpEJjLwp+HXToe us6+WPi82Se3KXHN71kjanBRQikEzau6qa626UD+gNy18v8oiut8en+ywsu08YwD qSyFMUW2NBj47glMN8e4cjCLDHz3BC8H8cujqGNZkAbXDXRUtvzFACRl3dt92ScW q9JNTiOSuJuuxXIqnmcOpIB3g7quS3aMU1EqTs/hGUBNmWNiMgmDfbx5/p+XQK/f NY4/H3gXgE7/1k6/kunp8zDIbbbuudbFsSPZIIT0ap8sbRYKk0M/Iiy2XwX5Iw5o 0a7VO+fkg4ZTHWsl3IadA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfeduledgjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeffleegieefgfevudehtdfhkeeutdffjeevgeffgeej vedthefgudeiteefheejheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jun 2024 10:32:04 -0400 (EDT) Message-ID: <8d268806-6162-4c31-a516-e3b1c13024b5@aklaver.com> Date: Fri, 14 Jun 2024 07:32:04 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Configure autovacuum To: "Shenavai, Manuel" , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/13/24 23:20, Shenavai, Manuel wrote: > Hi everyone, > > I would like to configure the autovacuum in a way that it runs very > frequently (i.e. after each update-statement). I tried the following Why? What is the problem you are trying to solve? > settings on my table: > > alter table mytable set (autovacuum_vacuum_scale_factor  = 0.0); > > alter table mytable set (autovacuum_vacuum_cost_delay  = 0.0); > > alter table mytable set (autovacuum_vacuum_cost_limit  = 10000); > > alter table mytable set (autovacuum_vacuum_threshold  = 1); > > I do a lot of updates on a single tuple and I would expect that the > autovacuum would start basically after each update (due to > autovacuum_vacuum_threshold=1). But the autovacuum is not running. > > Is it possible to configure postgres to autovacuum very aggressively > (i.e. after each update-statement)? > > Thanks in advance & > > Best regards, > > Manuel > -- Adrian Klaver adrian.klaver@aklaver.com