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 1m43xi-00070r-Sn for pgsql-hackers@arkaria.postgresql.org; Thu, 15 Jul 2021 16:11:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m43xh-0007P6-Se for pgsql-hackers@arkaria.postgresql.org; Thu, 15 Jul 2021 16:11:45 +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 1m43xh-0007Oy-12 for pgsql-hackers@lists.postgresql.org; Thu, 15 Jul 2021 16:11:45 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m43xe-0001BJ-U8 for pgsql-hackers@lists.postgresql.org; Thu, 15 Jul 2021 16:11:44 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 3D1B53200681; Thu, 15 Jul 2021 12:11:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 15 Jul 2021 12:11:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=UNXs2JFHqlDySpvuz6o0erAiRGTIGmlWp86xXk9sbzI=; b=mUBr3F+8 cxKgn6GT9+Qaos//qUzCk7aW6+FhYsUjePUmjpFoc7tMWQfZbHl/W24ub79dyxPX Hu7mi9uakstHKdTqvq7PUqcJpkVM5K/G8Qq+LYfJ4M+gbQ3XtUDZjj7f2fMXFZuz csSAjIkEkDq19zpEw/7CSF1xObyK/m/wFy2MaVFCqgCdkIfSZpOWw1zz4HDTCqol 0eCOY28Jus8tM0tYM7SJIg+JDblTmX2v8tQScOUFsbAzpZOzlV4goCGvnSs6gwo4 Gw8L2UnppT9oiD1srFrVELGCMhQ7l7HT0kY9XoYft+UVty4CtKz2KZF8M5RDohAw Y81E3yeJnbUHpA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddtgdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgrrhho ucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgheqne cuggftrfgrthhtvghrnhepudejveejffejveduudetvdekieeuiedtvdeileefkeevjedu feeguedvjefhueelnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomhenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgv rhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 15 Jul 2021 12:11:40 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 853352A099B; Thu, 15 Jul 2021 12:11:38 -0400 (-04) Date: Thu, 15 Jul 2021 12:11:38 -0400 From: Alvaro Herrera To: Dave Cramer Cc: "David G. Johnston" , Tom Lane , PostgreSQL Hackers Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly Message-ID: <202107151611.snkxhylndxpl@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Jul-15, Dave Cramer wrote: > Well IMHO the status quo is terrible. Perhaps you have a suggestion on how > to make it better ? I thought the suggestion of having pg_upgrade emit a file with a list of all extensions needing upgrade in each database was a fairly decent one. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/