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 1rn1pU-00BEgI-KA for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Mar 2024 19:42:29 +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 1rn1pS-007lMc-K8 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Mar 2024 19:42:27 +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 1rn1pS-007lMU-Bz for pgsql-bugs@lists.postgresql.org; Wed, 20 Mar 2024 19:42:26 +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 1rn1pK-005Xxg-TO for pgsql-bugs@lists.postgresql.org; Wed, 20 Mar 2024 19:42:25 +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=t1Q2ZipCr7HveulTYzNgkEFXDqK7M6Yw4gL6K1DzcDY=; b=DbZji UyZSSpR99rub7TNupCfy5TKKTsJjNhjZwGBEAA/E6TxX0aAgYm29LqCMqDGgsR457dgeS5rr024cE GuU91/KPZaQDeQfouR8AV0dG5gQrO0XxBNjyF0vmMy95nZVsA/X2FkGq41pexE6iq/DstmvQOLY/6 iRtDvdn1pzdC6hbtzk85+j0Ix0zgnbIVuTwRiRHRoxZ7Skz+mzlEpaRJZ1U6YTJQZFLj2aVZAzWOF TmuLgeVFzzTLVBt6fTpgslnPCTvGroBO6RlcCQwYt4IPk9GtZMqHtL/U243vmbxz3b3MuvEt5dze5 esmTF0DhIsoe19aQxULEPW5MAcu6g==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rn1pI-00Gy84-0H; Wed, 20 Mar 2024 15:42:16 -0400 Date: Wed, 20 Mar 2024 15:42:16 -0400 From: Bruce Momjian To: Wolfgang Walther Cc: Thomas Munro , peter@eisentraut.org, Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Tom Lane Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Message-ID: References: <4093813.1710899588@sss.pgh.pa.us> <4095435.1710900216@sss.pgh.pa.us> <477fa513-6bf0-456d-8d24-1e22a19df671@technowledgy.de> <1d11d75a-89cf-4e75-9c39-76bef37fc029@technowledgy.de> <203f8b3b-3a70-4342-80a2-a29650e6f6ed@technowledgy.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <203f8b3b-3a70-4342-80a2-a29650e6f6ed@technowledgy.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Mar 20, 2024 at 08:29:21PM +0100, Wolfgang Walther wrote: > Bruce Momjian: > > > The library/postgres docker image has been pulled about 8 billion times > > > since 2014 [1]. While we can't really tell how many of those pulled the > > > alpine variant of the image, comparing the alpine [2] and ubuntu/debian > > > [3,4] base images gives a rough estimate of >50% using alpine in general. > > > > Uh, what is the current behavior of Postgres on musl? It just fails if > > the process title is longer than argv[0] plus the environment space to > > the LD_ environment variable, and then linking fails for certain > > extensions? If there are many downloads, why would we only be getting > > this report now? > > The process title works fine. It's just the way how space is cleared for the > process title, that is causing problems elsewhere. > > The thing that is broken when running postgres on alpine/musl is, to put > libpq in a custom path and use LD_LIBRARY_PATH to find it when loading > libpqwalreceiver (+ some contrib modules). Nobody does that, especially not > in a container environment where postgres is likely the only thing running > in that container, so there is no point in using any custom library paths or > anything - the image is built once and made to work, and everybody else is > just using that working image. > > The much more practical problem is that the test suite doesn't run, because > it makes use of LD_LIBRARY_PATH for that purpose. In the past, the packagers > for alpine only disabled the failing tests, but IIRC they have given up on > that and just disabled the whole test suite by now. Thanks, that is very clear. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.