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 1qY86c-000rWc-Pa for pgsql-general@arkaria.postgresql.org; Mon, 21 Aug 2023 16:50:19 +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 1qY86a-008bmF-Fo for pgsql-general@arkaria.postgresql.org; Mon, 21 Aug 2023 16:50:16 +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 1qY86Z-008bkS-0H for pgsql-general@lists.postgresql.org; Mon, 21 Aug 2023 16:50:15 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY86U-000Cse-Nx for pgsql-general@postgresql.org; Mon, 21 Aug 2023 16:50:14 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id B4C925C26A4; Mon, 21 Aug 2023 12:50:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 21 Aug 2023 12:50:08 -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:sender:subject:subject:to:to; s=fm3; t= 1692636608; x=1692723008; bh=v0w3hSwTPO2Oo66LXu32h7h8bk3eeI3hvdf 0eJ0U1Ms=; b=jIlidN0Cqpy7Z7OwHKIFQzsCMptKcwKHC9IHAK8Fupk1wv3QGBo TJhvv0F9ZgSvueNYCRbm1xdctII+WsWdB6+eXkUQWn+gQiOBleYY82CWKfAqFTgN +HPz8zyWSCAYocCgGigbc+fv6MEs1++UDN0EfciQEWS/1y/jp8xAg0EX0pXVK8tf rCnSbfzVCYbR4PlG4NY9WBaFJkExHin/QfXlFYDoUov8V2GLlbaSQOx90C6A+Xmt BtAaWj4F6yxeAWDmOWUCyr1c176ZHrjkoMyXQA/g4noeQJLqaToAyRg2ZYD6mG3o RstYYqkMrkOOwFffwxgRPLfVq+Lfa4Cv1jg== 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:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1692636608; x= 1692723008; bh=v0w3hSwTPO2Oo66LXu32h7h8bk3eeI3hvdf0eJ0U1Ms=; b=d frv7zaUg8raVyNycaFR+oCLyxsIl5MbZVNLFRjF4Fmjt4dC5Ymnxw9TrIgLpM814 pe7B+Hd6GAUVhkOsRrvdEeM8K10oenyERo2fh0ceYxnUcvgDUSSDbrPKwAAA583o C8gu5k3SHhk5YVsB8bIrXCjYS/KOph/r6AeiTD3yB5DmQqo+C12ym1+PtVaVJ9n/ /GitIUqYd1E/LQQ6BDSr7kDcWm1wK727cIsM2TGtJeUtPJKqzJGaeCKmuTwsdp+v ryxkXId8BzovcEbmiqPU/HlJquYQhICId9ZLgCzl+43Qcgy2IlpetbxH7Ao3/XW2 wzMDwdraV8CsquoVWqNFw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudduledguddtiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepvedvkeeihfduhffhtdekleegffduiefgteejgeff gffhteefleeludfgleelgeevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Aug 2023 12:50:08 -0400 (EDT) Message-ID: <0ebcc8ea-7f5a-d014-d53f-e078622be35d@aklaver.com> Date: Mon, 21 Aug 2023 09:50:06 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: Why doesn't autovacuum/analyze run in due time after calling pg_stat_reset? Content-Language: en-US To: Rihad , pgsql-general General References: <69eacc0a-7e9b-4a35-278b-110b93d72882@mail.ru> <18167fbd-815f-9b43-7016-5e5bbb8fb255@gmail.com> <9440ab9c-4ee1-7668-5476-dc28e8086524@aklaver.com> <918f94be-41b9-e684-7679-b6bd819f693c@gmail.com> <9fed2b70-cc36-1239-d5b6-7a81afeafb82@aklaver.com> <329abf6c-2165-f410-717f-c20b3dd0a3d7@gmail.com> From: Adrian Klaver In-Reply-To: <329abf6c-2165-f410-717f-c20b3dd0a3d7@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/21/23 09:31, Rihad wrote: > On 8/21/23 20:17, Adrian Klaver wrote: >> On 8/21/23 09:09, Rihad wrote: >>> On 8/21/23 20:00, Adrian Klaver wrote: >> > > Sorry, they are all as per default, commented out in the config. > > There are no long running queries, otherwise they wouldn't be > vacuumed/analyzed in due time after running first manual analyze, which > updates n_live_tup to match reltuples. > My only remaining suggestion is to closely monitor the Postgres log and see if provides a clue. -- Adrian Klaver adrian.klaver@aklaver.com