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 1lV9vD-00046c-BR for pgsql-admin@arkaria.postgresql.org; Sat, 10 Apr 2021 09:28:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lV9uf-0008Rf-CB for pgsql-admin@arkaria.postgresql.org; Sat, 10 Apr 2021 09:28:21 +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 1lV9ue-0008RV-Va for pgsql-admin@lists.postgresql.org; Sat, 10 Apr 2021 09:28:21 +0000 Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lV9ua-0000iq-4a for pgsql-admin@lists.postgresql.org; Sat, 10 Apr 2021 09:28:17 +0000 Received: by mail-ej1-x629.google.com with SMTP id g5so5628703ejx.0 for ; Sat, 10 Apr 2021 02:28:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=wIla8R2+TYsD7gMwN3Ke3IWuinU5QDEdxYEsouiNhrs=; b=ne+yEoOX1H+HV9UDDOQ0qT8OsyNpZrPJujWLrI4ils0ciwq6yhf1yBUCiAI5vXV6bc y40v5FMYi5WYAb3RKIwNUJ8lAOahQ1IoZvlLjsAyXREkYnOy8cfot8f9Wcvq24ADSLSk NmnUCR5D6CNDvt8KCdfh6b/eo6Ot3xCEwn6Xkn5NgYMI3RKdas1FWF5tgR4tmfJnsLsR puobrbdQ6Xzz7Mhfl3y/Ei9hZuk28fPKZbN+yelW5PX+8hrskUtUR7aF2AYUc0/zhvG2 +OyyI8FNIEfMrLmyst5oubGBiGIUjij+lJzZwtR2ttx/PKmchO/gk4FMwr1T+WszUDuU 4aeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=wIla8R2+TYsD7gMwN3Ke3IWuinU5QDEdxYEsouiNhrs=; b=eqHrbIqv1vg37/EMwdyckjO1ELvRTarB3Fv3XqMSVP2pGnoRm1qXVtn9F7mFDz+nqM NieahsdAnymXyprA6DwW89/2/+5sPMB9HkdekVRt2+wCeDGTXIuFH4HDKYGXXvVyQVBw cazjqesOlqgmpd6Q3CWJhNycmPZIWykrb+1GM5RbGmRY2TTNkyXnI30U4xn2jtKfcd/k He9ObGEXS8N1UZZ/8OwJWZIDWIY2eGPkv75nltHCXrwJR99tVBEZo2l+2933z/6NIAsV 9WFg+h+qJXB6kBcDT6bVrn5W0gA8QuA0d07r0OZcZphok7GOsKqHlQ9S4MbN0b7YCmPO gLVA== X-Gm-Message-State: AOAM531/LRP10WsZENY7nSLLVulLM3WipRXTvDlQjdtz/BA3W4pgxR0x WEFTUJEODuu5L+nJ9KfAapaohA== X-Google-Smtp-Source: ABdhPJy7SRAtM4lfIAaQHRHjKKnO7y/ur4ir1V2x3/uirjtJXsqP1pRLN5sQAc6lh90t4CGEuVOkJg== X-Received: by 2002:a17:906:6d48:: with SMTP id a8mr247011ejt.92.1618046894150; Sat, 10 Apr 2021 02:28:14 -0700 (PDT) Received: from localhost.localdomain (62-47-148-75.adsl.highway.telekom.at. [62.47.148.75]) by smtp.gmail.com with ESMTPSA id w13sm2750831edc.81.2021.04.10.02.28.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 10 Apr 2021 02:28:13 -0700 (PDT) Message-ID: Subject: Re: autovacuum_vacuum_cost_limit From: Laurenz Albe To: Alvaro Herrera Cc: Henry Francisco Garcia Cortez , pgsql-admin@lists.postgresql.org, david.g.johnston@gmail.com Date: Sat, 10 Apr 2021 11:28:12 +0200 In-Reply-To: <20210410015023.GA13248@alvherre.pgsql> References: <20210410015023.GA13248@alvherre.pgsql> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2021-04-09 at 21:50 -0400, Alvaro Herrera wrote: > On 2021-Apr-10, Laurenz Albe wrote: > > On Fri, 2021-04-09 at 14:19 -0600, Henry Francisco Garcia Cortez wrote: > > > Hi community I have a question about autovacuum_vacuum_cost_limit > > > I want to increase this parameter I have read on internet that value > > > It could have as maximum 10,000 but I want to know, what will it be the troubles if I did that change > > > > That will keep PostgreSQL from functioning properly. > > I would never increase the setting beyond the 20ms that were the > > default before v12. > > I think you're confusing it with autovacuum_vacuum_cost_delay. He is > asking about the cost_limit. Increasing that setting will mean that the > 20ms sleeps will occur much less frequently. Yes, indeed. Sorry. Increasing "autovacuum_vacuum_cost_limit" will make autovacuum run faster. There is no problem with increasing it as much as you want. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com