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 1rosvV-003uED-Sj for pgsql-bugs@arkaria.postgresql.org; Mon, 25 Mar 2024 22:36:22 +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 1rosuV-008fes-Ps for pgsql-bugs@arkaria.postgresql.org; Mon, 25 Mar 2024 22:35:20 +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 1rosuV-008fek-Hf for pgsql-bugs@lists.postgresql.org; Mon, 25 Mar 2024 22:35:20 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rosuP-006TfD-0I for pgsql-bugs@lists.postgresql.org; Mon, 25 Mar 2024 22:35:19 +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=txrxF6e438ayyfvRhITbYDLAXtvmemDca7aqQzluijE=; b=WU+Py 3thX30bRDYEfZfkrqBlg5T2SbD8aBWxCurVSHsiN8/LDNapvHltYZYI9RnyiHj/RlwDVAsL+uBx6t 9ik4x2SA9wX4mCL07G0+tZfSBhGMziG8I6d9gLQsCA8N/oID+GqG2VIg77v/+ZSAclrQ4clp2Bwcs mBjFyafnyPcHDszxV2ba32zBrGlq2TCjuG+CQRA+j/dqvMWdVVwg6uT+aKk3x6CPKVx5CuFoZXe/L qcoKzwacs3u3bXxkt/kMb4fa3VZgWKEdEZruvX0/bIXP2vw0zfLehlhgGUQQ5MqeI1CDqrohLZlIG lQudLHWT7T2v/jZRwxFrNlKrwUPug==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rosuI-000iyu-2X; Mon, 25 Mar 2024 18:35:06 -0400 Date: Mon, 25 Mar 2024 18:35:06 -0400 From: Bruce Momjian To: walther@technowledgy.de Cc: Thomas Munro , Peter Eisentraut , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Tom Lane , 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2293691d-2adb-4502-b956-73e79dc43c55@technowledgy.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Mar 25, 2024 at 10:58:30PM +0100, walther@technowledgy.de wrote: > Bruce Momjian: > > With no one "hoping this patch dies in a fire"*, I have updated it with > > more details, which I now think is committable to master. Is this > > something to backpatch? Seems too rare a bug to me. > > 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. Also, in my patch, the parentheses here: #if defined(__linux__) && (! defined(__GLIBC__) && ! defined(__UCLIBC__)) are unnecessary so they should be removed: #if defined(__linux__) && ! defined(__GLIBC__) && ! defined(__UCLIBC__) I am only willing to apply my patch, and only to master. Other committers might be more willing. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.