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.96) (envelope-from ) id 1vT1ha-00Bfmx-2v for pgsql-committers@arkaria.postgresql.org; Tue, 09 Dec 2025 17:40:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vT1hZ-005rZe-0W for pgsql-committers@arkaria.postgresql.org; Tue, 09 Dec 2025 17:40:41 +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.96) (envelope-from ) id 1vT1hY-005rZV-32 for pgsql-committers@lists.postgresql.org; Tue, 09 Dec 2025 17:40:41 +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 1vT1hX-00459r-0U for pgsql-committers@lists.postgresql.org; Tue, 09 Dec 2025 17:40:40 +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 5B9HeJ3r251243; Tue, 9 Dec 2025 12:40:19 -0500 From: Tom Lane To: Heikki Linnakangas cc: Michael Paquier , Andrew Dunstan , pgsql-committers@lists.postgresql.org, Sami Imseih Subject: Re: pgsql: injection_points: Remove portions related to custom pgstats In-reply-to: References: <2899652.1765167313@sss.pgh.pa.us> <2904427.1765169854@sss.pgh.pa.us> Comments: In-reply-to Heikki Linnakangas message dated "Tue, 09 Dec 2025 15:24:39 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <251241.1765302019.1@sss.pgh.pa.us> Date: Tue, 09 Dec 2025 12:40:19 -0500 Message-ID: <251242.1765302019@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Heikki Linnakangas writes: > Hmm, using the first value of REGRESS is surprising. How about we change > the autoconf logic to match what meson does? As attached. Unless you want to back-patch that as far as 9.2, it's going to make matters worse not better for predictability of the DB names in the cross-version upgrade tests. I think it might be better to make the meson logic match the makefiles. Having said that, I think what we should be doing is adding whichever DB names we decide are problematic to the existing logic at about line 89 in AdjustUpgrade.pm: # remove dbs of modules known to cause pg_upgrade to fail # anything not builtin and incompatible should clean up its own db foreach my $bad_module ('adminpack', 'test_ddl_deparse', 'tsearch2') { if ($dbnames{"contrib_regression_$bad_module"}) { _add_st($result, 'postgres', "drop database contrib_regression_$bad_module"); delete($dbnames{"contrib_regression_$bad_module"}); } if ($dbnames{"regression_$bad_module"}) { _add_st($result, 'postgres', "drop database regression_$bad_module"); delete($dbnames{"regression_$bad_module"}); } } Perhaps another alternative is to add "DROP EXTENSION injection_points" at the end of the test scripts in the problematic modules. regards, tom lane