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 1rp1MU-004eoI-Tu for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Mar 2024 07:36:47 +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 1rp1MT-00C8TH-Av for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Mar 2024 07:36:45 +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 1rp1MT-00C8T9-2u for pgsql-bugs@lists.postgresql.org; Tue, 26 Mar 2024 07:36:45 +0000 Received: from dd25110.kasserver.com ([85.13.146.49]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rp1MR-006XoO-7Y for pgsql-bugs@lists.postgresql.org; Tue, 26 Mar 2024 07:36:44 +0000 Received: from [192.168.0.101] (ip-037-201-153-175.um10.pools.vodafone-ip.de [37.201.153.175]) by dd25110.kasserver.com (Postfix) with ESMTPSA id A5C2FE1A0085; Tue, 26 Mar 2024 08:36:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technowledgy.de; s=kas202308201259; t=1711438602; bh=WK1vhkMtcdKtUcrqUYGtTz1Nm6gRZrcN0StkV2FZiZk=; h=Date:From:Subject:To:Cc:References:In-Reply-To:From; b=YTXvcGyB/13VnqLjj0Cwj3TODyPoFUy3rMIQRzYEiRY+0olgbFUVAiogcPYtRY6i1 E9nT0jmsg1TgojhsMGIE4tKxvF8y1nElUQJCfMnfvxEMzTeLd0dlJOjMrwMq/NgPqU 5l//CK8NCStawoVIV9iNmm+rIfB93oGXpW8wLDueXNmMT1kHbR3HSINg9Vm2PIBn0T 6sot6xnk6HaCiDvf4YT90SimwiNDQRFANVEGLHmAu5PDucmh0LpGKCe/+KXv0hmhp7 6wVllBXyyJG2cFLQ5vr01/1E5LY2bQHS+LuIoQ66sqxOtSWSj9MvN2BeKwa4Ap8o5e vIfT1uWfr0YXQ== Message-ID: Date: Tue, 26 Mar 2024 08:36:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: walther@technowledgy.de Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Content-Language: en-US To: Bruce Momjian Cc: Thomas Munro , Peter Eisentraut , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Tom Lane , Robert Haas References: <36690fcf-f0c8-4d60-af49-6a7efa0e2b14@technowledgy.de> <2293691d-2adb-4502-b956-73e79dc43c55@technowledgy.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: / List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian: > You want to risk destabilizing Postgres by backpatching something this > complex so the regression tests can be run on all stable branches? I > think you are overestimating our desire to take on risk. I specifically wrote about backpatching the first (and maybe second) patch. None of that is risky. Patches 3-5 were not meant for backpatching at all. Best, Wolfgang