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 1rotdc-003xrI-Ij for pgsql-bugs@arkaria.postgresql.org; Mon, 25 Mar 2024 23:21:57 +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 1rotda-0092j1-So for pgsql-bugs@arkaria.postgresql.org; Mon, 25 Mar 2024 23:21:55 +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.94.2) (envelope-from ) id 1rotda-0092it-Kj for pgsql-bugs@lists.postgresql.org; Mon, 25 Mar 2024 23:21:55 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rotdX-006QBa-9F for pgsql-bugs@lists.postgresql.org; Mon, 25 Mar 2024 23:21:53 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=O2rryXmQFf4nT+6tc/2dDrzlxT83l7cBO0iCcUJOFac=; b=ljuvN l3bjJZsv7R3uDnltG1QV09LLuGV/CZ28rWFrzK6oMkT0EJKQX3/F4QrOObto6EDo0y6j4HXip3rCM y9sRvxxcf4srlsAfJKPQCgN4i5tjb3uA91bogYFEKynsgzek9Yd7DyqtJErCOl16pm4pTNxL66yM+ kVhiSTG51ktYOay0kz/6hz9XZaa+IOxT5eQ5n7cX0igEz9RC8rVLREIu228tnroZXxuHzKlKkHhPH m2Z+Dlyk7mtgvJ5nMYhfCVE7uyWCUaXohbjFxln96ELbd0UPsK0X+8CBd0YTRd7WKuNahgzrzwJ91 UfbfgdsF2WcMG22uSNGQYL+ueyK2g==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rotdU-000nJO-07; Mon, 25 Mar 2024 19:21:48 -0400 Date: Mon, 25 Mar 2024 19:21:48 -0400 From: Bruce Momjian To: Tom Lane Cc: walther@technowledgy.de, Thomas Munro , Peter Eisentraut , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Robert Haas Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Message-ID: References: <36690fcf-f0c8-4d60-af49-6a7efa0e2b14@technowledgy.de> <2293691d-2adb-4502-b956-73e79dc43c55@technowledgy.de> <2712255.1711408465@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2712255.1711408465@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Mar 25, 2024 at 07:14:25PM -0400, Tom Lane wrote: > Bruce Momjian writes: > > On Mon, Mar 25, 2024 at 10:58:30PM +0100, walther@technowledgy.de wrote: > >> I would like to see this backpatched to be able to run the regression tests > >> easily on all stable branches. > > > 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. > > If we want a buildfarm animal testing this platform, we kind of need > to support it on all branches. Having said that, I agree with you > that we are looking for a minimalist fix not a maximalist one. > I think the 0001 patch is about right, but the rest seem to be solving > problems we don't have. I could support the minimalist patch applied to all branches. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.