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 1tn9VE-002dS9-Di for pgsql-admin@arkaria.postgresql.org; Wed, 26 Feb 2025 04:58:36 +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 1tn9VD-00FGAw-Bj for pgsql-admin@arkaria.postgresql.org; Wed, 26 Feb 2025 04:58:35 +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 1tn9VD-00FGAo-0e for pgsql-admin@lists.postgresql.org; Wed, 26 Feb 2025 04:58:35 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tn9VA-0008YL-0D for pgsql-admin@lists.postgresql.org; Wed, 26 Feb 2025 04:58:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 51Q4wU591706948; Tue, 25 Feb 2025 23:58:30 -0500 From: Tom Lane To: Edwin UY cc: pgsql-admin@lists.postgresql.org Subject: Re: ANALYZE post-upgrade In-reply-to: References: Comments: In-reply-to Edwin UY message dated "Wed, 26 Feb 2025 17:39:25 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1706946.1740545910.1@sss.pgh.pa.us> Date: Tue, 25 Feb 2025 23:58:30 -0500 Message-ID: <1706947.1740545910@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Edwin UY writes: > The ANALYZE run post upgrade, that doesn't include having to run it on the > postgres database, does it? > It is only for the databases that you manually created for your application? You'd want to run it on any database with non-default contents. If you've created user tables in the postgres DB, they'd need analyzed. regards, tom lane