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 1s4Mke-003BMi-1x for pgsql-general@arkaria.postgresql.org; Tue, 07 May 2024 15:29:07 +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 1s4Mkb-003g7u-I7 for pgsql-general@arkaria.postgresql.org; Tue, 07 May 2024 15:29:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s4Mkb-003g7l-7K for pgsql-general@lists.postgresql.org; Tue, 07 May 2024 15:29:06 +0000 Received: from fout4-smtp.messagingengine.com ([103.168.172.147]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s4MkY-001tGl-Fp for pgsql-general@lists.postgresql.org; Tue, 07 May 2024 15:29:04 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 2AF4D1380D20; Tue, 7 May 2024 11:29:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 07 May 2024 11:29:01 -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=1715095741; x=1715182141; bh=kghKUGVKZIszpQlZ+RAZ0qlCH3ZoWB6x7SyvqrvR31M=; b= QldcgeIG+dYz5Sk5WDpan35yTXX8vhlkpYwzaLKVs8p7xKKPK4q10+ZG+3uOmwgx qr0QZ0pO7IKuNXWR9am3n6pYwkxw4U9eN/zdraNeGZYE/YF8NfbO58ywjViEg/gw 0Lcg7JjAESJhIBIf1jduZQz8jedWDGLL45w4HDRV8gF7LsB+KlXEgmIXkryAunOU 6F1ZAljsnsBuBc1By3Lj4so55ai6ysAYU1lLVfiJqVyPwMtZsLenwCIdj8ot2vPY QIateAJXdUpVNNKY4mTEMPRVa1gy3dKQ4Kty13Y8rYmDyjZpwCnmdXcywDITEtCf uOO4V296/LGD+TbMGzvp+A== 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=1715095741; x= 1715182141; bh=kghKUGVKZIszpQlZ+RAZ0qlCH3ZoWB6x7SyvqrvR31M=; b=V rMkscIayZQU4u9RWCXEZulrbZh3DsGKXyjkzsm6Q+um0xzhF/0C7zzva/TGeuAQX bAsolE33qVRvO/PueCtjVVuF2WMvofefmNHkNQzyhOapeaADEhfr671jURgMvOdT LzjzuY2bgL15JOBLvcHr6xuYEDJB1eFb8S5Ny+NVvvyh9YvyIIchNt76B/2K1eIN 3Objyjq78llR8mhMjutMarQtNvqauwuIItppBUjZMH/nGMp+N5iBTWd1UpsQyRc2 pW0qH4yOwL0OrgEeE83GTVYxHugRsBAIPkEMy+PRC7244X6PKWENor1g0hUVZrTF QwEBELjxx64lXnZkbjxDw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvkedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffhvfhfjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeffffeiueejheehjeeukeehtefgveffvdfhkeegledt fedtteeltddtjedtleehvdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 7 May 2024 11:29:00 -0400 (EDT) Message-ID: <399d1e23-db29-4dda-be55-8be41db48d3d@aklaver.com> Date: Tue, 7 May 2024 08:28:59 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Restore of a reference database kills the auto analyze processing. From: Adrian Klaver To: HORDER Philip , "pgsql-general@lists.postgresql.org" References: <5910d4dcbe244548bbf482dad0ceca83@uk.thalesgroup.com> <4b64d2cc-1df6-4982-b842-39fb0d886731@aklaver.com> <545ad7354f5f4c239df25faf8e883e98@uk.thalesgroup.com> <7c5b3f29-d82d-4cac-9aeb-8a4c0085ddf2@aklaver.com> Content-Language: en-US In-Reply-To: <7c5b3f29-d82d-4cac-9aeb-8a4c0085ddf2@aklaver.com> 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 5/7/24 08:24, Adrian Klaver wrote: > On 5/7/24 02:38, HORDER Philip wrote: >> Thanks for your time Adrian >> >> > > 1) What is the exact pg_restore command you are using? > > 2) From earlier post: '...  only analyzes tables in the new db at the > point of reload, then shuts off again.' Provide that sequence of events > from the Postgres log. > > 3) Also statistics from > > https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW > > for that table after the reload. 4) The autovacuum settings you have in effect. -- Adrian Klaver adrian.klaver@aklaver.com