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 1vSxi2-00AAlX-1L for pgsql-committers@arkaria.postgresql.org; Tue, 09 Dec 2025 13:24:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vSxi0-004kbX-31 for pgsql-committers@arkaria.postgresql.org; Tue, 09 Dec 2025 13:24:53 +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.96) (envelope-from ) id 1vSxi0-004kbO-21 for pgsql-committers@lists.postgresql.org; Tue, 09 Dec 2025 13:24:53 +0000 Received: from lahtoruutu.iki.fi ([2a0b:5c81:1c1::37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vSxhy-003w05-0S for pgsql-committers@lists.postgresql.org; Tue, 09 Dec 2025 13:24:52 +0000 Received: from [10.0.2.15] (unknown [130.41.208.2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hlinnaka) by lahtoruutu.iki.fi (Postfix) with ESMTPSA id 4dQfhm3VLJz49Q3m; Tue, 09 Dec 2025 15:24:40 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1765286681; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=y1owS9gaU3wrxYy72yrLnMglQD6oWihygQ9AW1hhFeE=; b=QsnftJgVTY5EvsSsN2DNC7CeVoES3TTnkV1tiGINit4J0XWtGozy4K0VL/MSggqX5qqIQu vryDsEzL573cFvhFKMS/5euM4vxaGS+4wrfRs0l/WVvtPW9Lg0iWK3U5/lEKqTJ0dZAlfL IUqw8K1K2AZK7h+9p2XuSiKY/Iswndocw+5DO2wC15CZjVwkXeWXt/kAG+xySFeiPmLlmg Xp3ZxTtEpVnGeRRVllyUIB57LKeINpva9MGiLBTWMXQeL6ahPNc6hx6hx01NarmSU0P4NP jaAvDYQ49v+ZrNwhcPEhGuh2OEHRMoyXA1wlj0ZHZ/QpmcxjBF4xouVMJeUl2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1765286681; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=y1owS9gaU3wrxYy72yrLnMglQD6oWihygQ9AW1hhFeE=; b=XWGaZAK4lU6RryjF/+yqFog6WRd8c+G6wqYBcLLqoXMc74Vic9sY/ve95UNEtVTREhTEUf GaXFMSSaO2eoF2zj9MPeBtSdKsXk2L3r1tKVLQK45KIjJAk8XsbanZZviW8mcLwsHhJuu7 fsT30fzT0ASzHzRFJhajFwBVXqSVoQF7aP6p03LAtQ1kiQEa7OuDLI1Ks+MRwHZx+zAmP5 UoyC7sL+s64hlolY7PH3mk+TpG1iw7rL/Ei4psL2RHyAUjDL5KHom0StJkvuvZJ02O0znO e6mANSNJdp4X2Df/VtldYNu/gr9PBaXmTCstlJcnIf1HQYbz1cieKXEu+hSd+Q== ARC-Seal: i=1; a=rsa-sha256; d=iki.fi; s=lahtoruutu; cv=none; t=1765286681; b=UrVbqtDRe/U6NbIaAsgXcNS80KfdqTr6uop4QLoqKDP/6qdE2Ymp2uZxTdUx6f+Eiz8+bd 2PXETI/eaeSMCnnWFJyUJ0mMGfVDcANagu6tbU/2V1mYgSrve+GvUV9se3YI5wOnWUdpoH ZK3pfUD0ZD4BRrtTXY4amoqS2MUFCbgWOkXOJFzeU/Uw3Fa+7JjSfkvwT2nVi+XrNAzGKi XCBSD8nkEsRV3oNywU/VwvurDmRAmcVRu+BRnXXLDONSVIWXdVK3lDjZ26jYMdLIJy2emQ zla/Tl8zNb8QquBHCQkYVcuu+be59iSrUjSRR7himfc9YXumk9DcFzlt1+S9qw== ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=hlinnaka smtp.mailfrom=hlinnaka@iki.fi Content-Type: multipart/mixed; boundary="------------vvZscuR62zdKfMqkyGEltQAu" Message-ID: Date: Tue, 9 Dec 2025 15:24:39 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgsql: injection_points: Remove portions related to custom pgstats To: Michael Paquier , Tom Lane Cc: Andrew Dunstan , pgsql-committers@lists.postgresql.org, Sami Imseih References: <2899652.1765167313@sss.pgh.pa.us> <2904427.1765169854@sss.pgh.pa.us> Content-Language: en-US From: Heikki Linnakangas In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------vvZscuR62zdKfMqkyGEltQAu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 08/12/2025 10:41, Michael Paquier wrote: > On Sun, Dec 07, 2025 at 11:57:34PM -0500, Tom Lane wrote: >> Nah, hold off till we have a discussion about whether the test is >> correct to expect compatibility. We can afford to have a couple >> of BF animals unhappy for a day or two while we come to a decision. > > By the way, while looking at the buildfarm failures, I have noticed > that something is wrong in my patch. Looking Makefile.global.in, > USE_MODULE_DB is built based on REGRESS for the tests of > src/test/modules/gin/. However things are inconsistent between meson > and ./configure. > > For example, this host uses configure/make: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2025-12-08%2006%3A08%3A23 > > The database name is contrib_regression_gin_incomplete_splits, which > points to the test gin_incomplete_split in src/test/modules/gin/, > meaning that my patch would not work. > > In the meson case, we got this failure: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-12-08%2006%3A27%3A04 > And here, the database name is regression_gin. > > When I looked at the buildfarm failures, I saw the regression_gin > first, wrote a patch based on that. But the second one based on > contrib_regression_gin_incomplete_splits was really puzzling me, until > I've noticed that the difference was configure vs meson for the two > hosts. So it seems to me that we have a second issue here, where > meson relies on a "name" while configure uses the first value of > "REGRESS". AdjustUpgrade.pm cannot know that it's dealing with one > build method or the other. In order to make my previous patch work, > we could use a DROP DATABASE IF EXISTS on both database names. That > would work, but that feels grotty for the purpose of fixing things, > especially as I don't see a point in keeping the test libraries across > major upgrades.. Hmm, using the first value of REGRESS is surprising. How about we change the autoconf logic to match what meson does? As attached. In the meson scripts, you can specify the database name explicitly by setting 'dbname'. It's only used in a few subdirs though. This in src/test/interfaces/ecpg/test/meson.build looks weird: > 'dbname': 'ecpg1_regression,ecpg2_regression', As far as I can tell, dbname is not a list, so I don't understand how that works. - Heikki --------------vvZscuR62zdKfMqkyGEltQAu Content-Type: text/x-patch; charset=UTF-8; name="derive-regression-db-name-like-meson-does.patch" Content-Disposition: attachment; filename="derive-regression-db-name-like-meson-does.patch" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL3NyYy9NYWtlZmlsZS5nbG9iYWwuaW4gYi9zcmMvTWFrZWZpbGUuZ2xv YmFsLmluCmluZGV4IDM3MWNkN2ViYTJjLi5jNmYwZTFlYjVlMSAxMDA2NDQKLS0tIGEvc3Jj L01ha2VmaWxlLmdsb2JhbC5pbgorKysgYi9zcmMvTWFrZWZpbGUuZ2xvYmFsLmluCkBAIC02 NzEsMTggKzY3MSw4IEBAIGVuZGlmCiAKIGlmbmVxICgkKFVTRV9NT0RVTEVfREIpLCkKICAg UExfVEVTVERCID0gcGxfcmVncmVzc2lvbl8kKE5BTUUpCi0gIGlmbmVxICgkKE1PRFVMRV9i aWcpLCkKLSAgICBDT05UUklCX1RFU1REQj1jb250cmliX3JlZ3Jlc3Npb25fJChNT0RVTEVf YmlnKQotICAgIElTT0xBVElPTl9URVNUREI9aXNvbGF0aW9uX3JlZ3Jlc3Npb25fJChNT0RV TEVfYmlnKQotICBlbHNlCi0gICAgaWZuZXEgKCQoTU9EVUxFUyksKQotICAgICAgQ09OVFJJ Ql9URVNUREI9Y29udHJpYl9yZWdyZXNzaW9uXyQod29yZCAxLCQoTU9EVUxFUykpCi0gICAg ICBJU09MQVRJT05fVEVTVERCPWlzb2xhdGlvbl9yZWdyZXNzaW9uXyQod29yZCAxLCQoTU9E VUxFUykpCi0gICAgZWxzZQotICAgICAgQ09OVFJJQl9URVNUREI9Y29udHJpYl9yZWdyZXNz aW9uXyQod29yZCAxLCQoUkVHUkVTUykpCi0gICAgICBJU09MQVRJT05fVEVTVERCPWlzb2xh dGlvbl9yZWdyZXNzaW9uXyQod29yZCAxLCQoSVNPTEFUSU9OKSkKLSAgICBlbmRpZgotICBl bmRpZgorICBDT05UUklCX1RFU1REQj1jb250cmliX3JlZ3Jlc3Npb25fJChub3RkaXIgJChz dWJkaXIpKQorICBJU09MQVRJT05fVEVTVERCPWlzb2xhdGlvbl9yZWdyZXNzaW9uXyQobm90 ZGlyICQoc3ViZGlyKSkKIGVsc2UKICAgUExfVEVTVERCID0gcGxfcmVncmVzc2lvbgogICBD T05UUklCX1RFU1REQiA9IGNvbnRyaWJfcmVncmVzc2lvbgo= --------------vvZscuR62zdKfMqkyGEltQAu--