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 1s7dje-006ane-5x for pgsql-general@arkaria.postgresql.org; Thu, 16 May 2024 16:13:39 +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 1s7djd-00BORG-Q3 for pgsql-general@arkaria.postgresql.org; Thu, 16 May 2024 16:13:37 +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 1s7djd-00BOR8-Ef for pgsql-general@lists.postgresql.org; Thu, 16 May 2024 16:13:37 +0000 Received: from wfout4-smtp.messagingengine.com ([64.147.123.147]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7djZ-000Z5z-BU for pgsql-general@lists.postgresql.org; Thu, 16 May 2024 16:13:36 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id CA80C1C0012B; Thu, 16 May 2024 12:13:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 16 May 2024 12:13:31 -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=fm2; t=1715876011; x=1715962411; bh=mNUYG+ed18H8auuP7TLI16mymzaOX0+G5YnAuFcSGdc=; b= fHsVaAIEmvYB4rBeUs8XF4qwQ0lCYbAzToxFkNttoUsU4YB9CvHEIM9Wnmlc9QTT 5c4MObqB14ZjwAq27RQH633tlWLRUe/voGhO1Ov4t4jUbuJ86sgWrOOoS9rE+DSx /YjGgTKS0Qd7rOyeYNd+UyLlizOrF299sXo2c1NmIRx0gUc+3xrZsmNGoLzqwYYB E1TU5hTYvVn19S11t+h6yqjNlVGrjj/T7Pi4d5qXKBPMMxj43OgVozC9RvO4K8Qn f1hzh1bYOtkmZOH5nuFOcMN87qah6kEJ3NW2XQWdb2346Rc6aTEXzuR788qqGfT2 G6GL5pc9E9H3J1pEkZwIbQ== 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=fm3; t=1715876011; x= 1715962411; bh=mNUYG+ed18H8auuP7TLI16mymzaOX0+G5YnAuFcSGdc=; b=Y rs2ZC5tXTyHQvKfr4H3WnXArWv/1eDZik5eegHmOaXVEqF+T5bg+AA2CT95BIuds 6GxN28mlJcRuQSYCVkyzxtjySu+pscwitGrX8RGWOBwHegDl98hDut2IVfFBWOnr Zr9nvu8if2b8TFTb0EJMICU19BMEmtLGJV1eVlXNGvtKRb83XhBgBobCs+k1thvg 4iSYcP9GuQTWMk0h7tJSDRKRwMxwPPUhGkpGl5OZiPNS2yWZGoGTTJAeru2Nx42e oosdrFNPL3Q0W/OURrZXuRRWG2rYPiuTwWhJsNM1d50X+DvILvp0/Q8rwsYnv4Go sWgruZlo1t5isgD+zH88A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdehuddgleeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeekfeehuddvjeeigfeifeejtdduudffledvfeelheef tdeiffeugfdvkeelgedtvdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 May 2024 12:13:30 -0400 (EDT) Message-ID: Date: Thu, 16 May 2024 09:13:29 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Restore of a reference database kills the auto analyze processing. To: HORDER Philip , "pgsql-general@lists.postgresql.org" References: Content-Language: en-US From: Adrian Klaver In-Reply-To: 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 5/16/24 08:59, HORDER Philip wrote: > Classified as: {OPEN} > > Adrian, > >> Still your contention was that autovacuum quit running after the initial restore and that is not the case.... > > This Postgres server has been restarted a few times since 2nd May most recently on Tuesday 14th, hence the more recent analyze status. Assuming clean shutdowns the statistics will survive restarts. They would be wiped when you drop a database and start over, have an unclean shutdown or you use one of the reset functions from here: https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-STATS-FUNCTIONS 28.2.25. Statistics Functions > > We've had some problems with our data feeds on this integration system, but these are now running again. > I'm planning to leave it all alone until I'm back in the office on Tuesday, and run this query again for a few tables and send you an update. > I'm expecting no further stats analysis, (and the performance to be appalling). From here: https://www.postgresql.org/docs/current/runtime-config-logging.html log_autovacuum_min_duration In addition, when this parameter is set to any value other than -1, a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. > > Thanks for your time. > > Phil Horder > Database Mechanic > > Thales > Land & Air Systems > > -- Adrian Klaver adrian.klaver@aklaver.com